Expandable data object management and indexing architecture for intersystem data exchange compatibility

ABSTRACT

A group-based communication platform is configured to ascertain the relatedness of various work objects shared among users of the group-based communication platform. Moreover, the group-based communication platform may further receive and process work objects originating from non-users of the group-based communication platform, thereby further expanding the utility of the determined relatedness between work objects. These work objects (or encrypted representations of these work objects) may be indexed and stored in association with the group-based communication platform, thereby enabling users to search for and retrieve work objects originating from a plurality of work object sources simultaneously, and based on various characteristics of those work objects and the determined interrelatedness between various work objects.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. application Ser. No.16/366,866, filed Mar. 27, 2019, which is incorporated herein byreference in its entirety.

BACKGROUND

Systems have been provided for facilitating communications among aplurality of individuals via message exchange across client devicesconnected with a centralized messaging system. However, historicalsystems have generally provided limited compatibility for communicationamong individuals utilizing discrete lines of communication.

Through applied effort, ingenuity, and innovation many deficiencies ofsuch systems have been solved by developing solutions that are inaccordance with the embodiments of the present invention, many examplesof which are described in detail herein.

BRIEF SUMMARY

Certain embodiments are directed to communication platformfunctionality—specifically group-based communication platformfunctionality—configured for inter-system operation with othercommunication platforms. Via the inter-system functionality, thegroup-based communication platform may grant users easy access to workobjects exchanged via any of a plurality of communication platforms.Moreover, in certain embodiments the group-based communication platformmay be configured to index various work objects (or encryptedrepresentations of work objects), thereby further facilitating useraccess to such work objects, for example, via search functionalities. Incertain embodiments, the group-based communication platform may beconfigured to generate and append supplemental metadata to each workobject received thereby, and the supplemental metadata may furtherfacilitate user identification of potentially relevant work objects. Forexample, topics may be assigned to particular work objects. Moreover,the group-based communication platform may be configured to generate awork object work graph to store data indicative of determinedrelationships between various work objects. Thus, when a user seeks workobjects relevant to a particular search query, work objects thatdirectly match that search query may be returned, as well as workobjects deemed sufficiently related to the search term (or deemedsufficiently related to other work objects satisfying the search query).

One embodiment is directed to a group-based communication platformconfigured for generating cache objects for local storage and localaccess by a client device. The group-based communication platform ofcertain embodiments comprises: one or more memory storage areas; and oneor more processors collectively configured to: receive one or more workobjects from a validated external resource for distribution to one ormore client devices via a group-based communication channel, wherein theone or more work objects comprise metadata and body content data;generate, based at least in part on the metadata, supplemental metadataidentifying the group-based communication channel and the one or moreclient devices; extract the body content data from the one or more workobjects; generate one or more cache objects each comprising at least aportion of the body content data and at least a portion of thesupplemental metadata for a corresponding work object; and disseminatethe one or more cache objects to the one or more client devicesidentified based at least in part on the supplemental metadata forstorage and access by the one or more client devices.

In various embodiments, generating one or more cache objects comprises:identifying, for each of the one or more work objects and based at leastin part on the metadata for a corresponding work object, a cache objecttemplate applicable to the corresponding work object; and populating atleast a portion of the cache object template with at least a portion ofthe body content data and the at least a portion of the supplementalmetadata for the corresponding work object.

In various embodiments, generating one or more cache objects comprises:generating a summary cache object comprising a first quantity of dataassociated with the work object, wherein the summary cache object isdisseminated to the one or more client devices in real time; andgenerating an expanded cache object comprising a second quantity of dataassociated with the work object, wherein the expanded cache object isdisseminated to the one or more client devices in response to a requestreceived from a client device of the one or more client devices.

Moreover, in certain embodiments, the one or more processors are furtherconfigured to index each of the one or more work objects within adatabase storage area. In various embodiments, the one or moreprocessors are further configured to execute a query function based atleast in part on a query request received from a client device of theone or more client devices, wherein the query function comprises:querying indexed content data, metadata, and supplemental data for aplurality of work objects based at least in part on the query request;rank one or more work objects based on relevance to the query request;and transmit cache objects to the requesting client device indicative ofthe ranked work objects identified during the search query.

In various embodiments, generating supplemental metadata comprisesassigning a topic to each of the one or more work objects. Moreover, incertain embodiments, disseminating the one or more cache objectscomprises: providing the one or more cache objects to a validatedexternal resource for distribution to one or more client devices viacommunication mechanisms of the validated external resource. In variousembodiments, providing the one or more cache objects to a validatedexternal resource for distribution to one or more client devicescomprises providing an email comprising the one or more cache objects toan email platform for disseminating as individual emails to the one ormore client devices.

In certain embodiments, the one or more work objects comprise event workobjects received from a validated external resource. Moreover, bodycontent data of the one or more event work objects may compriserecording data.

Another embodiment is directed to a computer-implemented method forgenerating cache objects for local storage and local access by a clientdevice, the method comprising: receiving one or more work objects from avalidated external resource for distribution to one or more clientdevices via a group-based communication channel, wherein the one or morework objects comprise metadata and body content data; generating, basedat least in part on the metadata, supplemental metadata identifying thegroup-based communication channel and the one or more client devices;extracting the body content data from the one or more work objects;generating one or more cache objects each comprising at least a portionof the body content data and at least a portion of the supplementalmetadata for a corresponding work object; and disseminating the one ormore cache objects to the one or more client devices identified based atleast in part on the supplemental metadata for storage and access by theone or more client devices.

In various embodiments, generating one or more cache objects comprises:identifying, for each of the one or more work objects and based at leastin part on the metadata for a corresponding work object, a cache objecttemplate applicable to the corresponding work object; and populating atleast a portion of the cache object template with at least a portion ofthe body content data and the at least a portion of the supplementalmetadata for the corresponding work object.

In various embodiments, generating one or more cache objects comprises:generating a summary cache object comprising a first quantity of dataassociated with the work object, wherein the summary cache object isdisseminated to the one or more client devices in real time; andgenerating an expanded cache object comprising a second quantity of dataassociated with the work object, wherein the expanded cache object isdisseminated to the one or more client devices in response to a requestreceived from a client device of the one or more client devices.Moreover, the method may further comprise indexing each of the one ormore work objects within a database storage area.

In certain embodiments, the method may comprise executing a queryfunction based at least in part on a query request received from aclient device of the one or more client devices, wherein the queryfunction comprises: querying indexed content data, metadata, andsupplemental data for a plurality of work objects based at least in parton the query request; rank one or more work objects based on relevanceto the query request; and transmit cache objects to the requestingclient device indicative of the ranked work objects identified duringthe search query.

In certain embodiments, generating supplemental metadata comprisesassigning a topic to each of the one or more work objects. In variousembodiments, disseminating the one or more cache objects comprises:providing the one or more cache objects to a validated external resourcefor distribution to one or more client devices via communicationmechanisms of the validated external resource.

In certain embodiments, providing the one or more cache objects to avalidated external resource for distribution to one or more clientdevices comprises providing an email comprising the one or more cacheobjects to an email platform for disseminating as individual emails tothe one or more client devices. In various embodiments, the one or morework objects comprise event work objects received from a validatedexternal resource. Moreover, body content data of the one or more eventwork objects may comprise recording data.

Another embodiment is directed to a computer program product comprisingat least one non-transitory computer-readable storage medium havingcomputer-readable program code portions stored therein, thecomputer-readable program code portions comprising an executable portionconfigured to cause a computer processor to: receive one or more workobjects from a validated external resource for distribution to one ormore client devices via a group-based communication channel, wherein theone or more work objects comprise metadata and body content data;generate, based at least in part on the metadata, supplemental metadataidentifying the group-based communication channel and the one or moreclient devices; extract the body content data from the one or more workobjects; generate one or more cache objects each comprising at least aportion of the body content data and at least a portion of thesupplemental metadata for a corresponding work object; and disseminatethe one or more cache objects to the one or more client devicesidentified based at least in part on the supplemental metadata forstorage and access by the one or more client devices.

In certain embodiments, generating one or more cache objects comprises:identifying, for each of the one or more work objects and based at leastin part on the metadata for a corresponding work object, a cache objecttemplate applicable to the corresponding work object; and populating atleast a portion of the cache object template with at least a portion ofthe body content data and the at least a portion of the supplementalmetadata for the corresponding work object.

In various embodiments, generating one or more cache objects comprises:generating a summary cache object comprising a first quantity of dataassociated with the work object, wherein the summary cache object isdisseminated to the one or more client devices in real time; andgenerating an expanded cache object comprising a second quantity of dataassociated with the work object, wherein the expanded cache object isdisseminated to the one or more client devices in response to a requestreceived from a client device of the one or more client devices.

In certain embodiments, the executable portion is further configured tocause the processor to index each of the one or more work objects withina database storage area. Moreover, the executable portion is may befurther configured to cause the processor to execute a query functionbased at least in part on a query request received from a client deviceof the one or more client devices, wherein the query function comprises:querying indexed content data, metadata, and supplemental data for aplurality of work objects based at least in part on the query request;rank one or more work objects based on relevance to the query request;and transmit cache objects to the requesting client device indicative ofthe ranked work objects identified during the search query.

In various embodiments, generating supplemental metadata comprisesassigning a topic to each of the one or more work objects.

Moreover, in certain embodiments, disseminating the one or more cacheobjects comprises: providing the one or more cache objects to avalidated external resource for distribution to one or more clientdevices via communication mechanisms of the validated external resource.

In various embodiments, providing the one or more cache objects to avalidated external resource for distribution to one or more clientdevices comprises providing an email comprising the one or more cacheobjects to an email platform for disseminating as individual emails tothe one or more client devices.

In certain embodiments, the one or more work objects comprise event workobjects received from a validated external resource. Moreover, bodycontent data of the one or more event work objects may compriserecording data.

Another embodiment is directed to a group-based communication platformconfigured for assigning a user expertise to a user identifier, thegroup-based communication platform comprising: one or more memorystorage areas; and one or more processors collectively configured to:receive one or more work objects from a validated external resource,wherein the one or more work objects comprise metadata and body contentdata; assign one or more topics to each of the one or more work objectsbased at least in part on the metadata and body content data; determinea subset of the one or more work objects associated with a useridentifier for a user; determine a level of relationship between theuser and each of the one or more event objects; and establish topicalexpertise associated with the user identifier based at least in part onthe topics of work objects associated with the user identifier and thelevel of relationship between the user and each of the event objects.

In certain embodiments, the one or more work objects comprise event workobjects, and wherein determining a level of relationship between theuser and each of the event work objects comprises determining whetherthe user participated in each of the one or more event work objects.Moreover, the one or more work objects comprise email work objects, andwherein determining a level of relationship between the user and each ofthe email work objects comprises determining whether the user was asending user of the email work objects. In various embodiments, the oneor more work objects comprise message work objects, and whereindetermining a level of relationship between the user and each of themessage work objects comprises determining whether the user was asending user of the message work objects.

In various embodiments, assigning a topic to each of the one or morework objects comprises utilizing Term frequency-inverse documentfrequency (Tf-Idf) analysis to identify one or more topics relevant toeach work object.

In various embodiments, each of the one or more work objects are eventobjects, and wherein the Tf-Idf analysis is performed on a recordingassociated with the work object.

Moreover, in certain embodiments, the one or more processors are furtherconfigured to generate a work graph identifying relationships betweeneach of the plurality of work objects, and wherein determining a levelof relationship between a user identifier and each of the one or morework objects comprises identifying relationships between work objectsassociated with the user identifier.

Another embodiment is directed to a computer-implemented method forassigning a user expertise to a user identifier, the method comprising:receiving one or more work objects from a validated external resource,wherein the one or more work objects comprise metadata and body contentdata; assigning one or more topics to each of the one or more workobjects based at least in part on the metadata and body content data;determining a subset of the one or more work objects associated with auser identifier for a user; determining a level of relationship betweenthe user and each of the one or more event objects; and establishingtopical expertise associated with the user identifier based at least inpart on the topics of work objects associated with the user identifierand the level of relationship between the user and each of the eventobjects.

In certain embodiments, the one or more work objects comprise event workobjects, and wherein determining a level of relationship between theuser and each of the event work objects comprises determining whetherthe user participated in each of the one or more event work objects.Moreover, the one or more work objects may comprise email work objects,and wherein determining a level of relationship between the user andeach of the email work objects comprises determining whether the userwas a sending user of the email work objects.

In certain embodiments, the one or more work objects comprise messagework objects, and wherein determining a level of relationship betweenthe user and each of the message work objects comprises determiningwhether the user was a sending user of the message work objects.Moreover, assigning a topic to each of the one or more work objects maycomprise utilizing Term frequency-inverse document frequency (Tf-Idf)analysis to identify one or more topics relevant to each work object.

In various embodiments, each of the one or more work objects are eventobjects, and wherein the Tf-Idf analysis is performed on a recordingassociated with the work object. Moreover, the method may furthercomprise generating a work graph identifying relationships between eachof the plurality of work objects, and wherein determining a level ofrelationship between a user identifier and each of the one or more workobjects comprises identifying relationships between work objectsassociated with the user identifier.

Another embodiment is directed to a computer program product comprisingat least one non-transitory computer-readable storage medium havingcomputer-readable program code portions stored therein, thecomputer-readable program code portions comprising an executable portionconfigured to cause a computer processor to: receive one or more workobjects from a validated external resource, wherein the one or more workobjects comprise metadata and body content data; assign one or moretopics to each of the one or more work objects based at least in part onthe metadata and body content data; determine a subset of the one ormore work objects associated with a user identifier for a user;determine a level of relationship between the user and each of the oneor more event objects; and establish topical expertise associated withthe user identifier based at least in part on the topics of work objectsassociated with the user identifier and the level of relationshipbetween the user and each of the event objects.

In various embodiments, the one or more work objects comprise event workobjects, and wherein determining a level of relationship between theuser and each of the event work objects comprises determining whetherthe user participated in each of the one or more event work objects.

Moreover, in certain embodiments, the one or more work objects compriseemail work objects, and wherein determining a level of relationshipbetween the user and each of the email work objects comprisesdetermining whether the user was a sending user of the email workobjects. In various embodiments, the one or more work objects comprisemessage work objects, and wherein determining a level of relationshipbetween the user and each of the message work objects comprisesdetermining whether the user was a sending user of the message workobjects.

In various embodiments, assigning a topic to each of the one or morework objects comprises utilizing Term frequency-inverse documentfrequency (Tf-Idf) analysis to identify one or more topics relevant toeach work object. Moreover, each of the one or more work objects areevent objects, and wherein the Tf-Idf analysis is performed on arecording associated with the work object. In certain embodiments, theexecutable portion is further configured to cause the processor togenerate a work graph identifying relationships between each of theplurality of work objects, and wherein determining a level ofrelationship between a user identifier and each of the one or more workobjects comprises identifying relationships between work objectsassociated with the user identifier.

Another embodiment is directed to a group-based communication platformconfigured for generating a work graph based on one or more workobjects, the group-based communication platform comprising: one or morememory storage areas; and one or more processors collectively configuredto: intake one or more work objects from a validated external resourcefor distribution to one or more client devices via at least one of oneor more group-based communication channels, wherein the one or more workobjects comprise metadata and body content data; determine a work objecttype for each of the one or more objects; extract work object data fromeach of the one or more work objects, wherein the work object dataextracted from each of the one or more work objects is identified basedat least in part on the work object type, and wherein the work objectdata is extracted from the metadata and the body content data; identify,based at least in part on the work object data, relationshipsestablished via each of the one or more work objects; establish, basedat least in part on the relationships established via each of the one ormore work objects; a work graph data structure interrelating one or morework objects shared via the group-based communication platform.

In various embodiments, the one or more processors are furtherconfigured to identify, based at least in part on the metadata and thecontent data, one or more topics assigned to each of the one or morework objects. Moreover, identifying one or more topics assigned to eachof the one or more work objects may comprise analyzing the metadata andthe body content data of each of the one or more work objects using aterm-frequency, inverse-document frequency analysis to identify relevantterms to be assigned as topics to each of the one or more work objects.

In certain embodiments, identifying relationships established via eachof the one or more work objects comprises at least one of: identifying aplurality of user identifiers associated with each of the one or morework objects and identifying relationships among the plurality of useridentifiers associated with each of the one or more work objects, andwherein establishing the work graph data structure comprisesinterrelating user identifiers based at least in part on relationshipsestablished via the one or more work objects; identifying a plurality ofchannel identifiers associated with each of the one or more work objectsand identifying relationships among the plurality of channel identifiersassociated with each of the one or more work objects, and whereinestablishing the work graph data structure comprises interrelatingchannel identifiers based at least in part on relationships establishedvia the one or more work objects; or identifying a plurality of topicsassociated with each of the one or more work objects and identifyingrelationships among the plurality of topics associated with each of theone or more work objects, and wherein establishing the work graph datastructure comprises interrelating topics based at least in part onrelationships established via the one or more work objects.

In various embodiments, the work graph establishes relationships among aplurality of work objects of different work object types. Moreover, theone or more processors may be further configured to intake one or morework objects received from one or more client devices for distributionvia the group-based communication platform.

In certain embodiments, the one or more processors are furtherconfigured to execute a query function based at least in part on a queryrequest received from a client device of the one or more client devices,wherein the query function comprises: querying work objects based atleast in part on the query request; rank one or more work objects basedon relevance to the query request and based on relatedness between workobjects as established within the work graph; and transmit cache objectsto the requesting client device indicative of the ranked work objectsidentified during the search query. Moreover, the one or more processorsmay be further configured to generate a neural network for executing asearch query based at least in part on the work graph.

Another embodiment is directed to a computer-implemented method forgenerating a work graph based on one or more work objects, the methodcomprising: intaking one or more work objects from a validated externalresource for distribution to one or more client devices via at least oneof one or more group-based communication channels, wherein the one ormore work objects comprise metadata and body content data; determining awork object type for each of the one or more objects; extracting workobject data from each of the one or more work objects, wherein the workobject data extracted from each of the one or more work objects isidentified based at least in part on the work object type, and whereinthe work object data is extracted from the metadata and the body contentdata; identifying, based at least in part on the work object data,relationships established via each of the one or more work objects;establishing, based at least in part on the relationships establishedvia each of the one or more work objects; a work graph data structureinterrelating one or more work objects shared via the group-basedcommunication platform.

In various embodiments, the method may further comprise identifying,based at least in part on the metadata and the content data, one or moretopics assigned to each of the one or more work objects. Moreover,identifying one or more topics assigned to each of the one or more workobjects may comprise analyzing the metadata and the body content data ofeach of the one or more work objects using a term-frequency,inverse-document frequency analysis to identify relevant terms to beassigned as topics to each of the one or more work objects.

In certain embodiments, identifying relationships established via eachof the one or more work objects comprises at least one of: identifying aplurality of user identifiers associated with each of the one or morework objects and identifying relationships among the plurality of useridentifiers associated with each of the one or more work objects, andwherein establishing the work graph data structure comprisesinterrelating user identifiers based at least in part on relationshipsestablished via the one or more work objects; identifying a plurality ofchannel identifiers associated with each of the one or more work objectsand identifying relationships among the plurality of channel identifiersassociated with each of the one or more work objects, and whereinestablishing the work graph data structure comprises interrelatingchannel identifiers based at least in part on relationships establishedvia the one or more work objects; or identifying a plurality of topicsassociated with each of the one or more work objects and identifyingrelationships among the plurality of topics associated with each of theone or more work objects, and wherein establishing the work graph datastructure comprises interrelating topics based at least in part onrelationships established via the one or more work objects.

In various embodiments, the work graph establishes relationships among aplurality of work objects of different work object types. Moreover, themethod may further comprise intaking one or more work objects receivedfrom one or more client devices for distribution via the group-basedcommunication platform.

In certain embodiments, executing a query function based at least inpart on a query request received from a client device of the one or moreclient devices, wherein the query function comprises: querying workobjects based at least in part on the query request; ranking one or morework objects based on relevance to the query request and based onrelatedness between work objects as established within the work graph;and transmit cache objects to the requesting client device indicative ofthe ranked work objects identified during the search query.

According to certain embodiments, the method further comprisesgenerating a neural network for executing a search query based at leastin part on the work graph.

Another embodiment is directed to a computer program product comprisingat least one non-transitory computer-readable storage medium havingcomputer-readable program code portions stored therein, thecomputer-readable program code portions comprising an executable portionconfigured to cause a computer processor to: intake one or more workobjects from a validated external resource for distribution to one ormore client devices via at least one of one or more group-basedcommunication channels, wherein the one or more work objects comprisemetadata and body content data; determine a work object type for each ofthe one or more objects; extract work object data from each of the oneor more work objects, wherein the work object data extracted from eachof the one or more work objects is identified based at least in part onthe work object type, and wherein the work object data is extracted fromthe metadata and the body content data; identify, based at least in parton the work object data, relationships established via each of the oneor more work objects; establish, based at least in part on therelationships established via each of the one or more work objects; awork graph data structure interrelating one or more work objects sharedvia the group-based communication platform.

In various embodiments, the executable portion is further configured tocause the computer processor to identify, based at least in part on themetadata and the content data, one or more topics assigned to each ofthe one or more work objects. In certain embodiments, identifying one ormore topics assigned to each of the one or more work objects comprisesanalyzing the metadata and the body content data of each of the one ormore work objects using a term-frequency, inverse-document frequencyanalysis to identify relevant terms to be assigned as topics to each ofthe one or more work objects. Moreover, identifying relationshipsestablished via each of the one or more work objects may comprise atleast one of: identifying a plurality of user identifiers associatedwith each of the one or more work objects and identifying relationshipsamong the plurality of user identifiers associated with each of the oneor more work objects, and wherein establishing the work graph datastructure comprises interrelating user identifiers based at least inpart on relationships established via the one or more work objects;identifying a plurality of channel identifiers associated with each ofthe one or more work objects and identifying relationships among theplurality of channel identifiers associated with each of the one or morework objects, and wherein establishing the work graph data structurecomprises interrelating channel identifiers based at least in part onrelationships established via the one or more work objects; oridentifying a plurality of topics associated with each of the one ormore work objects and identifying relationships among the plurality oftopics associated with each of the one or more work objects, and whereinestablishing the work graph data structure comprises interrelatingtopics based at least in part on relationships established via the oneor more work objects.

In certain embodiments, the work graph establishes relationships among aplurality of work objects of different work object types. Moreover, theexecutable portion may be further configured to cause the processor tointake one or more work objects received from one or more client devicesfor distribution via the group-based communication platform.

In certain embodiments, the executable portion is further configured tocause the processor to executing a query function based at least in parton a query request received from a client device of the one or moreclient devices, wherein the query function comprises: querying workobjects based at least in part on the query request; ranking one or morework objects based on relevance to the query request and based onrelatedness between work objects as established within the work graph;and transmitting cache objects to the requesting client deviceindicative of the ranked work objects identified during the searchquery.

In certain embodiments, the executable portion is further configured tocause the processor to generate a neural network for executing a searchquery based at least in part on the work graph.

Another embodiment is directed to a group-based communication platformconfigured for indexing personal work objects within a database storagearea, the group-based communication platform comprising: one or morememory storage areas; and one or more processors collectively configuredto: intake one or more personal work objects from a client deviceassociated with a specific user identifier, wherein the one or morepersonal work objects comprise content data and metadata designatingeach of the one or more personal work objects as personal to thespecific user identifier; extract work object data from each of the oneor more personal work objects; define links for each of the one or morepersonal work objects within an existing work graph data structureinterrelating the one or more personal work objects with other workobjects represented within the existing work graph data structure; andindex the one or more personal work objects for retrieval by the clientdevice associated with the specific user identifier based at least inpart on characteristics of the one or more personal work objectsidentified by the defined links.

In certain embodiments, the one or more processors are furtherconfigured to represent the one or more personal work objects asencrypted work objects within the work graph data structure. In variousembodiments, the characteristics of the one or more personal workobjects may be determined based at least in part on a term-frequency,inverse-document frequency analysis to identify relevant terms to beassigned as topics for each of the one or more personal work objects.Moreover, the one or more personal work objects may comprise tasks. Incertain embodiments, the links are defined between work objects ofdiffering work object types.

In various embodiments, the one or more processors are furtherconfigured to execute a query function based at least in part on a queryrequested received from the client device associated with the specificuser identifier, wherein the query function comprises: querying workobjects based at least in part on the query request; rank one or morework objects based on relevance to the query request and based onrelatedness between work objects as established within the work graph,wherein the one or more ranked work objects comprise at least one of theone or more personal work objects; and transmit cache objects to therequesting client device indicative of the one or more ranked workobjects identified during the search query.

In certain embodiments, the one or more processors are furtherconfigured to generate a neural network for executing a search querybased at least in part on the work graph.

Another embodiment is directed to a computer-implemented method forindexing personal work objects within a database storage area, themethod comprising: intaking one or more personal work objects from aclient device associated with a specific user identifier, wherein theone or more personal work objects comprise content data and metadatadesignating each of the one or more personal work objects as personal tothe specific user identifier; extracting work object data from each ofthe one or more personal work objects; defining links for each of theone or more personal work objects within an existing work graph datastructure interrelating the one or more personal work objects with otherwork objects represented within the existing work graph data structure;and indexing the one or more personal work objects for retrieval by theclient device associated with the specific user identifier based atleast in part on characteristics of the one or more personal workobjects identified by the defined links.

In certain embodiments, the method further comprises representing theone or more personal work objects as encrypted work objects within thework graph data structure.

In various embodiments, the characteristics of the one or more personalwork objects may be determined based at least in part on aterm-frequency, inverse-document frequency analysis to identify relevantterms to be assigned as topics for each of the one or more personal workobjects. In certain embodiments, the one or more personal work objectscomprise tasks. Moreover, the links may be defined between work objectsof differing work object types.

In certain embodiments, the method further comprises executing a queryfunction based at least in part on a query requested received from theclient device associated with the specific user identifier, wherein thequery function comprises: querying work objects based at least in parton the query request; rank one or more work objects based on relevanceto the query request and based on relatedness between work objects asestablished within the work graph, wherein the one or more ranked workobjects comprise at least one of the one or more personal work objects;and transmit cache objects to the requesting client device indicative ofthe one or more ranked work objects identified during the search query.

In certain embodiments, the method further comprises generating a neuralnetwork for executing a search query based at least in part on the workgraph.

Another embodiment is directed to a computer program product comprisingat least one non-transitory computer-readable storage medium havingcomputer-readable program code portions stored therein, thecomputer-readable program code portions comprising an executable portionconfigured to cause a computer processor to: intaking one or morepersonal work objects from a client device associated with a specificuser identifier, wherein the one or more personal work objects comprisecontent data and metadata designating each of the one or more personalwork objects as personal to the specific user identifier; extractingwork object data from each of the one or more personal work objects;defining links for each of the one or more personal work objects withinan existing work graph data structure interrelating the one or morepersonal work objects with other work objects represented within theexisting work graph data structure; and indexing the one or morepersonal work objects for retrieval by the client device associated withthe specific user identifier based at least in part on characteristicsof the one or more personal work objects identified by the definedlinks.

In certain embodiments, the computer program product is furtherconfigured to cause the computer processor to represent the one or morepersonal work objects as encrypted work objects within the work graphdata structure.

In various embodiments, the characteristics of the one or more personalwork objects may be determined based at least in part on aterm-frequency, inverse-document frequency analysis to identify relevantterms to be assigned as topics for each of the one or more personal workobjects.

Moreover, the one or more personal work objects comprise tasks. Invarious embodiments, the links are defined between work objects ofdiffering work object types. In certain embodiments, the executableportion is further configured to cause the processor to execute a queryfunction based at least in part on a query requested received from theclient device associated with the specific user identifier, wherein thequery function comprises: querying work objects based at least in parton the query request; rank one or more work objects based on relevanceto the query request and based on relatedness between work objects asestablished within the work graph, wherein the one or more ranked workobjects comprise at least one of the one or more personal work objects;and transmit cache objects to the requesting client device indicative ofthe one or more ranked work objects identified during the search query.In various embodiments, the executable portion is further configured tocause the processor to generate a neural network for executing a searchquery based at least in part on the work graph.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 shows an example environment in which various embodimentsoperate;

FIG. 2 shows an example schematic configuration of an operation serveraccording to one embodiment;

FIG. 3 shows an example schematic configuration of an interfacecomputing interface according to one embodiment;

FIG. 4 shows an example schematic configuration of a platform interfaceaccording to one embodiment;

FIG. 5 shows an example data flow attributable to a message work objectaccording to one embodiment;

FIG. 6 shows an example data flow attributable to an email work objectaccording to one embodiment;

FIGS. 7A-7B show example cache objects attributable to an email workobject according to one embodiment;

FIGS. 8-9 show example data flows attributable to a call work objectaccording to various embodiments;

FIGS. 10A-10G show example cache objects attributable to calls inaccordance with various embodiments;

FIG. 11 shows an example data flow attributable to an appointmentaccording to one embodiment;

FIG. 12 shows an example cache object attributable to an appointmentwork object according to one embodiment;

FIG. 13 shows an example data flow attributable to a file according toone embodiment;

FIG. 14 shows an example data flow attributable to a task according toone embodiment;

FIG. 15 is a flowchart showing an example process for generating a workgraph according to one embodiment; and

FIG. 16 is an example illustration of relationships between work objectsas may be represented by a work graph in accordance with one embodiment.

DETAILED DESCRIPTION

The present disclosure more fully describes various embodiments withreference to the accompanying drawings. It should be understood thatsome, but not all embodiments are shown and described herein. Indeed,the embodiments may take many different forms, and accordingly thisdisclosure should not be construed as limited to the embodiments setforth herein. Rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Like numbersrefer to like elements throughout.

Overview

Various embodiments provide data object management and indexingarchitectures provided in association with work object exchangeplatforms, such as group-based communication platforms or externalresources (such as validated external resources), that are capable ofseamlessly exchanging specific data objects (specifically, work objects,discussed herein) among a plurality of otherwise incompatiblecommunication platforms, thereby facilitating communication betweenindividuals (e.g., users of one or more of these communicationplatforms) and creating a work-object-agnostic indexing system enablingusers to quickly and easily locate needed work objects, regardless oftheir type or primary communication pathway. As specific examples,emails, events (including calls, video-calls, VoIP calls, in-personmeetings, single-user appointments, and/or other events), messages,files, and/or other work objects may be transitioned betweencommunication platforms or other platforms (e.g., from a group-basedcommunication platform to an email platform, or vice versa; from agroup-based communication platform to an event calendar platform, orvice versa; and/or the like) seamlessly, thereby expanding the potentialuniverse of communication platform users that may be contacted andexpanding the potential universe of work objects that may be searchedand/or utilized to construct one or more work graphs, which may beillustrative of relationships between and/or among various work objects.Such a work graph may be leveraged via machine-learning and/orartificial-intelligence configurations to present users with expansive,relevant results to search queries (e.g., with an integrated rankinghierarchy to indicate levels of relevance to the user's search query),to automatically connect or introduce users of one or more communicationplatforms with other users and/or with automatically curated topicalcontent, and/or the like.

Certain embodiments provide an integrated work object exchangeplatform—also referred to herein as a group-based communication platformfor exchanging one or more specific work object types (e.g., messages,files, and/or the like) between users of the group-based communicationplatform (e.g., via client devices operated by each user). Work objectsexchanged through the integrated work object exchange platform may benaturally indexed through internal methodologies such that these workobjects may be easily retrieved in response to relevant queries. Otherwork objects, such as work objects primarily exchanged via third partycommunication platforms may be received into the work object exchangeplatform via one or more intake mechanisms configured to ensure properwork object routing (e.g., to ensure the received work object isdisseminated to appropriate client devices and/or external communicationnetworks) and indexing to facilitate work object searching and usage foridentifying relationships among various work objects for generating awork graph.

Definitions

As used herein, the terms “data,” “content,” “information,” and similarterms may be used interchangeably to refer to data capable of beingtransmitted, received, and/or stored in accordance with embodiments ofthe present invention. Thus, use of any such terms should not be takento limit the spirit and scope of embodiments of the present invention.Further, where a computing device is described herein to receive datafrom another computing device, it will be appreciated that the data maybe received directly from another computing device or may be receivedindirectly via one or more intermediary computing devices, such as, forexample, one or more servers, relays, routers, network access points,base stations, hosts, and/or the like. Similarly, where a computingdevice is described herein to send data to another computing device, itwill be appreciated that the data may be sent directly to anothercomputing device or may be sent indirectly via one or more intermediarycomputing devices, such as, for example, one or more servers, relays,routers, network access points, base stations, hosts, and/or the like.Moreover, data may be transmitted, received, or otherwise exchanged asindividual “data objects” comprising interrelated data. Data objects mayconstitute single bits of data or large quantities of interrelated data,such as substantive data (e.g., the underlying content to be conveyedthrough a communication) and associated metadata (e.g., data nototherwise considered to be substantive data, encompassingcharacteristics of the substantive data and/or the relevant exchange(e.g., the identity of the user sending the data, the identity of theuser receiving the data, the time/date when the data was sent,formatting to be associated with the exchanged substantive data, thefile type of the data object, and/or the like).

Data objects may be take many forms, including as work objects, as userprofile objects, as channel profile objects, and/or the like. Asutilized herein, “work objects” are embodied as electronic data objectsspecifically executable and/or otherwise accessible via the group-basedcommunication platform 105 and/or at least one validated externalresource 112A-112N. Work objects may be received at the group-basedcommunication platform 105 by receiving those work objects conveyed to(pushed to) the group-based communication platform 105, or thegroup-based communication platform 105 may retrieve (pull to) variouswork objects stored within accessible storage areas of one or moreclient devices 101A-101N, 102, validated external resources 112A-112N,and/or the like. The work objects may convey human-readablerepresentations of information and/or computer-executable content thatcauses a particular client device 101A-101N, 102 to operate in aparticular way. Specifics of certain work objects examples are discussedherein, however it should be understood that in certain embodiments,work objects may be embodied as emails, events, audio files, videofiles, document files, spreadsheet files, presentation files, tasks,and/or the like; as well as any contextual data corresponding therewith.Work objects may thus be non-personal (alternatively referred to aspublic) as they are exchanged between a plurality of users or otherwisemade available to a plurality of users. Alternatively, work objects maybe personal in nature (e.g., as defined by a portion of metadataassociated with the work object), such that access to the content of thework object is limited to a single user (or a limited number of definedusers). For example, work objects personal to a single user mayencompass tasks or task lists defined personally by and for a particularuser. Access to personal work objects may be limited to access requestsassociated with defined user identifiers. In certain embodiments,personal work objects may be represented as encrypted data when indexedin database storage areas and/or when included within work graph datastructures including personal and non-personal work objects.

The term “work object contextual data” refers to data that is extractedor derived from a work object that may affect how the work object isdetermined to relate to other work objects. As discussed herein, workobject contextual data comprises metadata, such as title/subjectinformation, date and time information, work object owner/creatorinformation, work object type information (e.g., file, email, call,image, ticket, task, etc.), work object detail information thatcomprises text, images, audio, and file attachments, objects attached tothe event (e.g., audio, file, video, tasks) and/or one or morepredefined work object data fields. The work object contextual data mayfurther include a validated external resource identifier, a useridentifier, one or more group-based communication channel identifiersassociated with group-based communication channels that the user hasbeen granted access to, one or more group identifiers for groups withwhich the user is associated, message identifier, event identifier, orexternal work object identifier. The group-based communication systemmay be configured to further facilitate indexing the work objectcontextual data.

In certain embodiments, work objects include external work objectsand/or internal work objects. The terms “external work object” or“remote work object” refer to a data structure or a dataset that isreceived from a validated external resource (defined below) to agroup-based communication platform for representing files, calls, tasks,events, notifications, calendar events, emails, contacts, directories(or directory entries), and/or the like that a validated externalresource transmits, posts, or shares for rendering to a group-basedcommunication interface. An external work object is associated with auser of a client device (either communicating directly with agroup-based communication platform or communicating within and/orthrough a validated external resource).

The terms “internal work object” or “group-based communication workobject” refer to a data structure or a dataset created by thegroup-based communication platform and reflects data about files, calls,tasks, events, messages, notifications, calendar events, contacts,directories (or directory entries), and/or emails posted by agroup-based communication channel member to a group-based communicationinterface. An internal work object comprises a file object, a callobject, a task object, an event object, a message object, a notificationobject, an internal calendar event, an internal contact object, aninternal directory object, an internal directory entry object, and/orthe like. The internal work object is associated with one or more of agroup-based communication channel member, a group-based communicationmessage, a group-based communication channel, and another external orinternal work object.

A “work graph” is a graph-based knowledge representation data structureapplied to the group-based communication platform data corpus thatcomprises relationships between users, between various data objects,such as between work objects, between users and work objects, betweengroup-based communication channels and work objects, between topics andwork objects, between users and group-based communication channels,between users and topics, between group-based communication channels andtopics, between group-based communication channels, between topics,and/or the like. Attributes of work graph data may be represented asnodes while associations between such attributes are represented asedges. Work graph data may be used as machine learning (ML) structureinputs for training and/or utilizing ML structures (e.g., logisticregressions, neural networks, etc.). The group-based communicationsystem may utilize work object metadata, channel metadata, and/or MLstructures to rank work objects, users, channels, and/or the like for avariety of applications. For example, such applications may includeprioritizing the most relevant work objects to a user's search query andpresenting those most relevant work objects in response to a searchquery.

The term “user” should be understood to refer to an individual, a groupof individuals, business, organization, and the like. Users may access agroup-based communication platform (and/or other platform, such as avalidated external resource) using client devices. “Group-based” is usedherein to refer to a system, channel, message, or virtual environmentthat has security sufficient such that it is accessible only to adefined group of users. The group may be defined by common accesscredentials such as those of an organization or commercial enterprise.Access may further be facilitated by a validated request to join or aninvitation to join transmitted by one group member user to anothernon-member user. Group identifiers (defined below) are used to associatedata, information, messages, etc., with specific groups.

The terms “user profile,” “user account,” and “user account details”refer to information associated with a user, including, for example, auser identifier, one or more communication channel identifiersassociated with communication channels that the user has been grantedaccess to, one or more group identifiers for groups with which the useris associated, an indication as to whether the user is anowner/administrator of any communication channels, an indication as towhether the user is an owner/administrator of any groups, an indicationas to whether the user has any communication channel restrictions, aplurality of messages, a plurality of emojis, a plurality ofconversations, a plurality of conversation topics, an avatar, an emailaddress, a real name (e.g., John Doe), a username (e.g., jdoe), apassword, a time zone, a status, and the like. The user account detailscan include a subset designation of user credentials, such as, forexample, login information for the user including the user's usernameand password. As noted above, user profiles may be one type of dataobject.

The term “client device” refers to computer hardware(s) and/orsoftware(s) that is/are configured to access one or more services madeavailable by one or more servers. The server(s) is/are often (but notalways) on another computer system, in which case the client deviceaccesses the service by way of a network. A client device may beassociated with a unique user identifier, which may be referenced in oneor more data tables providing an electronic indication that suggests agroup (e.g., a user group) and/or communication channel to which theuser of the client device belongs to. Client devices may include,without limitation, smart phones, tablet computers, laptop computers,desktop computers, wearable devices, personal computers, enterprisecomputers, and the like.

The term “group-based communication platform” refers to a collection ofcomputing services that are accessible to one or more client devices,and that are operable to provide access to a plurality of softwareapplications related to operations of databases. In some examples, thegroup-based communication platform may take the form of one or morecentral servers disposed in communication with one or more additionalservers running software applications, and having access to one or moredatabases storing digital content items, application-related data,and/or the like.

The term “communication pathway” refers to an information route andassociated circuitry that is used for data exchange between and amongsystems and parts of systems. For example, a communication pathway maybe established between and among various client devices, allowing theseclient devices to communicate and share data between and among eachother. Communication pathways may be intra-system communication pathwaysenabling communication only between users of the same communicationplatform (e.g., email between one or more email users; group-basedmessaging between one or more group-based communication platform users;and/or the like) or inter-system communication pathways enablingcommunication between and/or among one or more distinct communicationplatforms.

As a specific example, a communication pathway of certain embodimentsencompasses a “communication channel,” which refers to an informationroute and associated circuitry that is used for data exchange betweenand among client devices via a group-based communication platform. Workobjects may be exchanged over a communication channel exclusively, orvia other communication pathways. Where a communication channel isutilized to exchange work objects, specific processes may be utilizedfor disseminating work objects to user-members of the communicationchannel (e.g., to the users' client devices 101A-101N). Moreover,specific processes may be utilized for further disseminating workobjects to client devices 102 that do not have direct access to the dataexchanged within the communication channel, if applicable. Thesecommunication channels may be “group-based communication channels”established between and among a select group of client devices (andtheir respective users) for sharing messages among all users of thegroup. The communication channels may also and/or alternatively beone-to-one, direct message communication channels established betweenand among two client devices (and their respective users) for sharingmessages among only those two users. Communication channels may beembodied as a portion of intra-system communication pathways in certaininstances.

The term “channel settings” refers to various defined or definableparameters of a group-based communication channel. The channel settingsmay comprise a channel identifier, a channel name string, and a channelpurpose string. Moreover, the channel settings may be indicative ofwhether a particular communication channel is an intra-systemcommunication pathway or an inter-system communication pathway.

Multiple communication channels may operate on each of one or morecomputing devices having access to the group-based communicationplatform, and therefore a “communication channel identifier” or “channelidentifier” may be assigned to a communication channel, which indicatesthe physical address in a database where related data of thatcommunication channel is stored and which is utilized to identify clientdevices that participate within the communication channel to receivedata exchanged on the communication channel. The communication channelidentifier therefore ensures communication channels remain distinct andseparate even on computing devices associated with a plurality ofcommunication channels. In other embodiments, other communicationpathways may be accessed via discrete portals, apps (e.g., computerprograms) and/or the like, each with their own identifyingcharacteristics.

The channel name string refers to a data structure containing a stringof alphanumerical characters for identifying a channel in non-technicalterms. The channel name string may be identical to a channel identifier,however this is not required in certain embodiments. A channel purposestring refers to a data structure containing a string of alphanumericalcharacters that indicates to a group-based communication platform and/ora user a purpose of the group-based communications channel. In someexamples, a channel purpose string may contain a channel purpose such as“to work on project Nucleus.” Channel settings may also include amessage retention window that indicates a period of network time duringwhich messages associated with a group-based communication channel areretained within a group-based communication repository. Upon expirationof the period of network time (i.e., the message retention window), amessage or file associated with the message retention window may bedeleted from a group-based communication repository.

Channel settings may also indicate the number and/or identity of groups(or users) authorized to access the particular group-based communicationchannel; and, when applicable one or more group identifier values thatindicate the group identifier(s) of one or more groups authorized toaccess the group-based communication channel. In some embodiments, if auser associated with a client device attempts to access a group-basedcommunication channel and the user capacity has been reached, the clientdevice may not be permitted to access the group-based communicationchannel. The channel settings may also include one or more authorizedapplication identifiers that indicate to a group-based communicationplatform which applications are authorized to be downloaded and utilizedin the group-based communication channel. In embodiments, if anapplication attempts to access a group-based communication channel andthe application is not associated with an authorized applicationidentifier, the application may not be granted access to the group-basedcommunication channel.

A communication channel may be “public,” which may allow any clientdevice to join and participate in the information sharing through thecommunication channel. Public communication channels may still be accesslimited, for example, to user identifiers associated with a particulargroup identifier. Thus, in the context of a large organization, publiccommunication channels may be accessible to all employees of theorganization, but those same public communication channels may not beaccessible to non-employees of the organization (associated with useridentifiers that are not associated with the identifier of the largeorganization). A communication channel may be “private,” which mayrestrict data communications in the communication channel to certainclient devices and/or users.

The term “viewing interface” refers to a virtual communicationsenvironment, feed, and/or display configured to display work objectsexchanged via a communication platform. For example, a viewing interfacemay be embodied as and/or accessible via an email client (e.g., Gmail,Microsoft Outlook, Hotmail, and/or the like). As another example, aviewing interface may be an electronic calendar (e.g., Google Calendar,iCal, Microsoft Outlook, and/or the like).

As a specific example, a viewing interface may be embodied as a“communication channel interface,” which refers to a virtualcommunications environment or feed accessible to users of thegroup-based communication platform that is configured to displaymessaging communications (and/or other work objects)posted/shared/transmitted by channel members (e.g., validated usersaccessing the environment using client devices) that are viewable onlyto the members of the group. The format of the communication channelinterface may appear differently to different members of the group-basedcommunication channel; however, the content of the communication channelinterface (i.e., messaging communications) will be displayed to eachmember of the group-based communication channel. For instance, a commonset of group-based messaging communications will be displayed to eachmember of the respective group-based communication channel such that thecontent of the communication channel interface (i.e., messagingcommunications) will not vary per member of the group-basedcommunication channel.

As used herein, the terms “messaging communication” and “message” referto any electronically generated work object provided by a user using aclient device and that is configured for display within a communicationchannel interface. Message communications may include any text, image,video, audio, or combination thereof provided by a user (using a clientdevice). For instance, the user may provide a messaging communicationthat includes text as well as an image and a video within the messagingcommunication as message contents. In such a case, the text, image, andvideo would comprise the messaging communication or digital contentobject. Each message sent or posted to a communication channel (e.g., agroup-based communication channel) of the group-based communicationplatform includes metadata comprising the following: a sending useridentifier, a message identifier, message contents, an objectidentifier, a group identifier and/or a communication channelidentifier. Each of the foregoing identifiers may comprise ASCII text, apointer, a memory address, and the like.

“Groups” or “teams” refer to particular organizations, collections ofusers, or other defining characteristics utilized to associate aplurality of users. Groups or teams may be distinguished based on “groupidentifiers” or “team identifiers” that refer to one or more items ofdata by which a group within a group-based communication platform may beidentified. As an example, a group identifier may comprise ASCII text, apointer, a memory address, and the like. These group identifiers may bestored within group profiles. A group profile may comprise a uniquegroup identifier for each group, a group name for each group, adate/time at which a particular group was created, a unique useridentifier having administrative user privileges for a particular group,and/or the like. As discussed herein, groups or teams may extend toencompass both users of the group-based communication platform and usersof alternative communication platforms (e.g., email users).

A “sending user identifier” is associated with a collection of workobjects that are sent by a particular user (i.e., a client deviceassociated with the particular user). These messages may be analyzed todetermine context regarding the user (e.g., the user's topical expertiseor interest in a topic may be determined based on the frequency ofmention of the topic or key words associated with the topic within suchmessages, and the user's topical expertise may be assigned to the useridentifier).

The term “private communication channel” refers to a communicationchannel with restricted access such that it is not generally accessibleand/or searchable by other members of the group-based communicationplatform. For example, only those users or administrators who haveknowledge of and permission to access (e.g., the user identifier of aparticular user is associated with a communication channel identifierfor the private communication channel after the user has beenvalidated/authenticated) the private communication channel may viewcontent of the private communication channel.

“Interface computing entities” as discussed herein with reference tovarious embodiments are computing devices (or portions of computingdevices) for maintaining communication connections with various clientdevices. Specifically, interface computing entities may be configuredfor maintaining data connections (e.g., websocket connections) initiatedby each of a plurality of client devices for transmitting messages(e.g., object updates) and corresponding metadata (e.g., comprisingobject identifiers) in real time between operation servers of thegroup-based communication platform and respective client devices. Incertain embodiments, the interface computing entities generate andmaintain backend connections with one or more operation servers asdiscussed herein for obtaining messages to be disseminated to thevarious client devices.

“Operation servers” as discussed herein with reference to certainembodiments are computing devices configured for interacting withvarious client devices (e.g., via an interface computing entity) forreceiving and/or disseminating work objects among client devices.Operation servers may be configured to receive, generate, store (in anassociated database), and/or direct messages received from and/ordisseminated to users (e.g., via corresponding client devices). Thefunctionality of the operation servers may be provided via a singleserver or collection of servers having a common functionality, or thefunctionality of the operation servers may be segmented among aplurality of servers or collections of servers performing subsets of thedescribed functionality of the operation servers. For example, a firstsubset of operation servers—gateway servers—may be configured forreceiving messages from client devices and/or for transmitting messagesto client devices via an interface computing entity. These gatewayservers may be in communication with a second subset of operationservers—channel servers—configured for collecting messages distributedwithin communication channels and for storing those messages within amessage repository database for indexing and archiving. In certainembodiments, the channel servers may be in communication with theinterface computing entities to provide various messages to clientdevices. Moreover, a third subset of operation servers—interoperationservers—may be specifically configured for ensuring seamlesscommunication of work objects received from and disseminated to one ormore validated external resources.

The terms “validated external resource,” “validated external resources,”or “validated remote resource” refer to a software program, application,platform, or service that is configured to communicate with thegroup-based communication platform for providing service to a clientdevice (e.g., via a group-based communication interface). The validatedexternal resource operates on a compiled code base or repository that isseparate and distinct from that which supports the group-basedcommunication platform. The validated external resources of someembodiments generate work objects (specifically, external work objects,discussed herein) executable or otherwise usable by features of thevalidated external resource. In other embodiments, the group basedcommunication platform passes work objects (e.g., internal work objects,discussed herein) to the validated external resources. In someembodiments, the validated external resource may communicate with thegroup-based communication platform, and vice versa, through one or moreapplication program interfaces (APIs). For example, the group-basedcommunication platform may subscribe to an API of the validated externalresource that is configured to transmit one or more external workobjects. In some embodiments, the validated external resource receivestokens or other authentication credentials that are used to facilitatesecure communication between the validated external resource and thegroup-based communication platform in view of group-based communicationplatform network security layers or protocols (e.g., network firewallprotocols).

The term “external resource entity identifier” refers to one or moreitems of data by which a user of an external resource may be uniquelyidentified by a group-based communication platform. For example, anexternal resource entity identifier may comprise American Standard Codefor Information Interchange (ASCII) text, a pointer, a memory address,and the like. One or more external resource entity identifiers may bestored to a limited profile of a group-based communication platformalong with other identifiers (e.g., user identifier, group identifiers,group-based communication channel identifiers, etc.). The externalresource entity identifier may be embodied in a format native to theexternal resource to which it is associated or may be structured in aformat designated by the group-based communication platform. In certainembodiments, the external resource entity identifier further identifiesthe validated external resource to which the external resource entityidentifier applies. Correlating one or more external resource entityidentifiers to a user account or user identifier of the group-basedcommunication platform allows the group-based communication platform tolink accounts from disparate external resources with a selectedgroup-based communication platform user account.

The term “event occurrence,” “event object,” or “event” refers to a dataobject, a data structure, a data set, or collection of data andinstructions that collectively represents a work object of an validatedexternal resource (in which case an event occurrence is an externalevent occurrence embodied as an external work object) or of thegroup-based communication platform (in which case an event occurrence isan internal event occurrence embodied as an internal work object)providing scheduling features. Each event occurrence encompassescontextual data comprising metadata and/or content data associated withthe event occurrence. The form and use of the contextual data of theevent occurrence may vary between different validated externalresources. One example of a standard defining data structure for eventoccurrence data objects and calendar data exchange is the iCalendarstandard, known more formally as the Internet Calendaring and SchedulingCore Object Specification, RFC 2445. In the iCalendar standard, calendardata is stored in the top-level object, known as the Calendaring andScheduling Core Object.

The contextual data comprises an event identifier that uniquelyidentifies a particular created event occurrence. The contextual data ofan event occurrence of certain embodiments is embodied as an eventoccurrence data structure comprising a plurality of event occurrenceparameters, including the event identifier. Each event occurrenceparameter may be one of an event occurrence timestamp, an eventoccurrence location identifier, an event occurrence start timeidentifier, an event occurrence run time identifier, an event occurrencecompletion indicator, an event occurrence creator identifier, an eventoccurrence invite identifier, an event occurrence acceptance identifier,an event occurrence decline identifier, an event occurrence acceptanceidentifier, and event occurrence title. In embodiments, an eventoccurrence is an electronic representation of a live in-person eventduring which one or more attendees gather or collaborate for aparticular duration of time. In various embodiments, the live in-personevent occurs at one or more physical locations and/or involves audioand/or video connections for said collaboration. As discussed herein,the context data may be supplemented with supplemental metadata, forexample, upon generation of a recording for a particular event.

The term “event identifier” refers to one or more items of data by whichan event occurrence may be uniquely identified. For example, an eventidentifier may comprise ASCII text, a pointer, a memory address, and/orthe like.

The term “event occurrence data structure” or “event data structure”refers to a collection of data associated with an event occurrencecapable of being transmitted, received, and/or stored. In variousembodiments, the event occurrence data structure may comprise aplurality of event occurrence parameters. In various embodiments, theevent occurrence data structure may be associated with one or moregroup-based communication channel identifiers.

The term “event occurrence parameter” or “event parameter” refers to acollection of data that defines one or more aspects of an eventoccurrence. In various embodiments, an event occurrence parameter may beone of an event identifier, an event occurrence timestamp, an eventoccurrence location identifier, an event occurrence start timeidentifier, an event occurrence run time identifier, an event occurrencecompletion indicator, an event occurrence invitee identifier, an eventoccurrence invitation acceptance identifier, an event occurrenceinvitation decline identifier, or event occurrence attendee/participantidentifier, an event occurrence title, an event occurrence attachment,and/or the like.

The term “event occurrence timestamp” or “event timestamp” refers to adigital representation of network time associated with at least one ofthe receipt, commencement, conclusion or run time of an eventoccurrence. The event occurrence timestamp may comprise a digitalrepresentation of one or more of the network time at which the eventoccurrence was created by the event occurrence creator, the network timeat which the event occurrence was scheduled to begin, the network timeat which the event was scheduled to end, the network time at which theevent occurrence actually began, the network time at which the eventoccurrence actually ended, and the actual event occurrence run time. Thetimestamp may be analyzed to determine context regarding the eventoccurrence (e.g., the exact moment at which the event occurrenceconcluded and the proximity of that moment to the group-basedcommunication message timestamp of a group-based communication messagethat was sent in a group-based communication channel).The eventoccurrence timestamp may be associated with an event identifier. Thetimestamp may be analyzed to determine context regarding the event(e.g., the exact moment at which the event started and/or ended, as wellas the corresponding event run time). In various embodiments, the eventtimestamp may be an event occurrence parameter.

The term “event occurrence creator identifier” or “event creatoridentifier” refers to one or more items of data by which an eventoccurrence creator that creates an event occurrence may be uniquelyidentified. For example, an event occurrence creator identifier maycomprise a validated external resource identifier (as discussed herein)or a user identifier. In various embodiments, the event occurrencecreator identifier may be associated with a client device and a userprofile within a group-based communication system.

The term “event occurrence invitee identifier” or “event inviteeidentifier” refers to one or more items of data by which an eventoccurrence invitee may be uniquely identified. An event occurrenceinvitee identifier may be associated with a user who receives aninvitation to participate in an event occurrence and has the option toeither accept or decline the invitation. For example an event occurrenceinvitee identifier may comprise a validated external resource identifier(as discussed herein) or a user identifier. In various embodiments, theevent occurrence invitee identifier may be an event occurrenceparameter.

The term “event occurrence invitation acceptance identifier” or “eventinvitation acceptance identifier” refers to one or more items of data bywhich an event occurrence invitation acceptance may be uniquelyidentified. An event occurrence invitation acceptance identifier may beassociated with a user (i.e., an event occurrence invitee associatedwith an event occurrence invitee identifier) who receives an invitationto participate in an event occurrence associated with an eventoccurrence creator identifier and accepts the invitation. Accordingly,an event occurrence invitation acceptance identifier is associated withan event occurrence invitee identifier. For example an event occurrenceinvite acceptance identifier may comprise ASCII text, a pointer, amemory address, and the like. In various embodiments, the eventoccurrence invite acceptance identifier may be an event occurrenceparameter.

The term “event occurrence invitation decline identifier” or “eventinvitation decline identifier” refers to one or more items of data bywhich an event occurrence invitation decline may be uniquely identified.An event occurrence invitation decline identifier may be associated witha user (i.e., an event occurrence invitee associated with an eventoccurrence invitee identifier) who receives an invitation to participatein an event occurrence associated with an event occurrence creatoridentifier and declines the invitation. Accordingly, an event occurrenceinvitation decline identifier is associated with an event occurrenceinvitee identifier. For example an event occurrence invite declineidentifier may comprise ASCII text, a pointer, a memory address, and thelike. In various embodiments, the event occurrence invite declineidentifier may be an event occurrence parameter.

The term “event occurrence attendee identifier,” “event occurrenceparticipant identifier,” “event attendee identifier” or “eventparticipant identifier” refers to one or more items of data by which anevent occurrence attendee may be uniquely identified. An eventoccurrence attendee may be a user (i.e., an event occurrence inviteeassociated with an event occurrence invitee identifier) who actuallyattends/participates in an event occurrence associated with an eventoccurrence creator identifier. Accordingly, an event occurrence attendeeidentifier is associated with an event occurrence invitee identifier. Inembodiments, an event occurrence attendee identifier is distinct fromand independent of both an event occurrence invitation acceptanceidentifier and an event occurrence invitation decline identifier. Thatan event occurrence invitee either accepts or declines an eventoccurrence invite is a digital representation of the invitee's intentionor lack thereof to participate in the event occurrence; such anacceptance or decline does not necessarily affect whether or not thatinvitee actually participates in the event occurrence. For example anevent occurrence attendee identifier may comprise ASCII text, a pointer,a memory address, and the like. In various embodiments, the eventoccurrence attendee identifier may be an event occurrence parameter.

The term “event occurrence title” or “event title” refers to an eventoccurrence creator designated title associated with an event occurrence.In various embodiments, the event occurrence title may be representativeof a purpose or topic associated with the event occurrence. In variousembodiments, the event occurrence title may be analyzed to determine itsrelation to a conversation topic or a content topic for the purposes ofdetecting conversations and content associated with an event occurrence.For example, the event occurrence title may comprise one or more stringsof text or other characters (e.g., emojis).

In certain embodiments, one or more of the interface computing entitiesand/or the operation servers may be geographically distributed, forexample, to service client devices located geographically proximate theone or more computing entities. However, in certain embodiments thevarious computing entities (including the interface computing entitiesand/or the operation servers) may be centrally-located.

Example System Architecture

Methods, apparatuses, and computer program products of the presentinvention may be embodied by any of a variety of devices. For example,the method, apparatus, and computer program product of an exampleembodiment may be embodied by a network device, such as a server orother network entity, configured to communicate with one or moredevices, such as one or more client devices. In some preferred andnon-limiting embodiments, the computing device may include fixedcomputing devices, such as a personal computer or a computerworkstation. Still further, example embodiments may be embodied by anyof a variety of mobile devices, such as a portable digital assistant(PDA), mobile phone, smartphone, laptop computer, tablet computer,wearable device, or any combination of the aforementioned devices.

FIG. 1 illustrates an example computing environment within which variousembodiments may operate. Users may access, share, and/or retrieve dataobjects (e.g., work objects) associated with the group-basedcommunication platform 105 via a communication network 103 using clientdevices 101A-101N having direct access to the group-based communicationplatform 105, and/or using client devices 102 having access to one ormore validated external resources 112A-112N, such as email systems,calendar systems, and/or the like.

Communication network 103 may include any wired or wirelesscommunication network including, for example, a wired or wireless localarea network (LAN), personal area network (PAN), metropolitan areanetwork (MAN), wide area network (WAN), or the like, as well as anyhardware, software and/or firmware required to implement it (such as,e.g., network routers, etc.). For example, communication network 103 mayinclude a cellular telephone, an 802.11, 802.16, 802.20, and/or WiMaxnetwork. Further, the communication network 103 may include a publicnetwork, such as the Internet, a private network, such as an intranet,or combinations thereof, and may utilize a variety of networkingprotocols now available or later developed including, but not limited toTCP/IP based networking protocols. As discussed herein, the networkingprotocol is configured to enable data transmission via websocketcommunications. For instance, the networking protocol may be customizedto suit the needs of the group-based communication platform. In someembodiments, the protocol is a custom protocol of JSON objects sent viaa websocket channel. In some embodiments, data may be transmitted via aplurality of protocols, such as JSON over RPC, JSON over REST/HTTP, andthe like.

In the illustrated embodiment, the group-based communication platform105 includes a plurality of operation servers 107A-107N configured fordisseminating work objects via an interface computing entity 109 and/ora platform interface 111. Collectively, the operation servers 107A-107Nare configured for receiving work objects transmitted from one or moreclient devices 101A-101N, 102 (primarily through the group-basedcommunication platform 105 and/or primarily through one or morevalidated external resources 112A-112N), storing the work objects withindatabase storage areas 108A-108N for dissemination and indexing, and/orfor transmitting messages to appropriate client devices 101A-101N, 102via an interface computing entity 109 and/or platform interface 111 viaone or more validated external resources 112A-112N.

Similarly, the interface computing entity 109 (or plurality of interfacecomputing entities 109) may be embodied as a computer or computers asknown in the art. In the illustrated embodiment of FIG. 1, the interfacecomputing entity 109 provides for receiving electronic data from varioussources, including, but not limited to the client devices 101A-101N(e.g., via websocket communications over the communications network 103)and/or the operation servers 107A-107N (e.g., via backendcommunications). Moreover, the interface computing entity 109 of theillustrated embodiment is also configured to parse metadata provided asa portion of one or more electronic work objects (e.g., messages), andto direct incoming electronic work objects to one or more operationservers 107A-107N based at least in part on the content of the metadataassociated with the electronic work objects and/or to direct outboundelectronic messages to one or more client devices 101A-101N based atleast in part on the content of the metadata associated with theelectronic work objects.

Platform interface 111 may similarly provide work object distributionand receiving functionality, however platform interface 111 may bespecifically configured for communicating with validated externalresources 112A-112N, such as email platforms, calendar platforms, and/orthe like. Accordingly, platform interface 111 may be configured forgenerating and/or maintaining various Application Program Interfaces(APIs) (e.g., Representational state Transfer (REST) APIs), one or moreproxy endpoints accessible via defined URLs to specific ones of theplurality of validated external resources 112A-112N, and/or the like,such that data objects—specifically work objects—may be seamlesslyshared between users of the group-based communication platform 105(e.g., via their respective client devices 101A-101N) and users of oneor more validated external resources 112A-112N (e.g., via theirrespective client devices 102).

The client devices 101A-101N, 102 may be any computing device as definedabove. Work objects exchanged between the operation servers 107A-107Nand the client devices 101A-101N via the interface computing entity 109may be provided in various forms and via various methods.

In some preferred and non-limiting embodiments, one or more of theclient devices 101A-101N, 102 are mobile devices, such as smartphones ortablets. One or more of the client devices 101A-101N, 102 interact withthe group-based communication platform 105 and/or one or more validatedexternal resources (or other third party systems) via an “app”executable on the client devices 101A-101N, 102. For example, an app maybe provided that executes on mobile device operating systems such asApple Inc.'s iOS®, Google Inc.'s Android®, or Microsoft Inc.'s Windows10 Mobile®. A client device 101A-101N, 102 may store a plurality of appseach stored in memory and executable thereon. Each of the plurality ofapps may correspond to a particular platform. For example, a first appstored on a client device is utilized to communicate with thegroup-based communication platform 105 and a second app stored on theclient device is utilized to communicate with a first validated externalresource 112A.

In certain embodiments, client devices 101A-101N interacting directlywith the group-based communication platform 105 execute an app tointeract with the operation servers 107A-107N and/or interface computingentity 109. Those client devices 102 interacting directly with validatedexternal resources 112A-112N may similarly execute an app to interactwith the respective validated external resources 112A-112N. Such appsare typically designed to execute on mobile devices, such as smartphonesor tablets. For example, an app may be provided that executes on mobiledevice operating systems such as Apple Inc.'s iOS®, Google Inc.'sAndroid®, or Microsoft Inc.'s Windows 10 Mobile®. These platformstypically provide frameworks that allow apps to communicate with oneanother, and with particular hardware and software components of mobiledevices. For example, the mobile operating systems named above eachprovides frameworks for interacting with location services circuitry,wired and wireless network interfaces, user contacts, and otherapplications. Communication with hardware and software modules executingoutside of the app is typically provided via application programminginterfaces (APIs) provided by the mobile device operating system. Thus,via the app executing on the client devices 101A-101N, these clientdevices 101A-101N are configured for communicating with the group-basedcommunication platform 105 via one or more websockets.

In some preferred and non-limiting embodiments, the client devices101A-101N may interact with the operation servers 107A-107N and/orinterface computing entity 109 via a web browser. The client devices101A-101N may also include various hardware or firmware designed tointeract with the operation servers 107A-107N and/or interface computingentity 109. Again, via the browser of the client devices 101A-101N, theclient devices 101A-101N are configured for communicating with thegroup-based communication platform 105 via one or more websockets.

Similarly, client devices 102 may interact with the validated externalresources 102A-102N via a web browser. The client devices 102 may alsoinclude various hardware or firmware designed to interact with thevalidated external resources 102A-102N (e.g., via websockets or othercommunication protocols).

Example Apparatuses Utilized with Various Embodiments

Each operation server 107 may be embodied by one or more computingsystems, such as apparatus 200 shown in FIG. 2. The apparatus 200 mayinclude processor 202, memory 204, input/output circuitry 206,communications circuitry 208, and message amplifier circuitry 210. Theapparatus 200 may be configured to execute the operations describedherein with respect to FIGS. 1-15. Although these components 202-210 aredescribed with respect to functional limitations, it should beunderstood that the particular implementations necessarily include theuse of particular hardware. It should also be understood that certain ofthese components 202-210 may include similar or common hardware. Forexample, two sets of circuitries may both leverage use of the sameprocessor, network interface, storage medium, or the like to performtheir associated functions, such that duplicate hardware is not requiredfor each set of circuitries.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 204 via a bus forpassing information among components of the apparatus. The memory 204 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 204 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 204 may be configured to store information, data,content, applications, instructions, or the like for enabling theapparatus to carry out various functions in accordance with exampleembodiments of the present invention.

The processor 202 may be embodied in a number of different ways and may,for example, include one or more processing devices configured toperform independently. In some preferred and non-limiting embodiments,the processor 202 may include one or more processors configured intandem via a bus to enable independent execution of instructions,pipelining, and/or multithreading. The use of the term “processingcircuitry” may be understood to include a single core processor, amulti-core processor, multiple processors internal to the apparatus,and/or remote or “cloud” processors.

In some preferred and non-limiting embodiments, the processor 202 may beconfigured to execute instructions stored in the memory 204 or otherwiseaccessible to the processor 202. In some preferred and non-limitingembodiments, the processor 202 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 202 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 202 is embodied as an executor of software instructions, theinstructions may specifically configure the processor 202 to perform thealgorithms and/or operations described herein when the instructions areexecuted.

As just one example, the processor 202 may be configured to maintain oneor more communication channels connecting a plurality of client devices101A-101N to enable work object sharing/dissemination therebetween. Theprocessor 202 ensures that work objects (e.g., messages) intended forexchange between the client devices 101A-101N within the particularcommunication channel are properly disseminated to those client devices101A-101N for display within respective display windows provided via theclient devices 101A-101N. Moreover, with reference to FIG. 1, theprocessor 202 may be configured to appropriately cause one or more workobjects to be disseminated to one or more client device 102communicating via one or more validated external resources 112A-112N(e.g., email, external messaging systems, and/or the like), throughplatform interface 111.

Moreover, the processor 202 may be configured to synchronize workobjects exchanged on a particular communication channel with one or moredatabase storage areas 108A-108N for storage and/or indexing of workobjects therein. Collectively, the plurality of work objects (e.g., bothinternal work objects and external work objects) define a work objectcorpus that may be utilized to perform various search query functionsand/or as historical data that may be utilized in accordance withmachine learning and/or artificial intelligence algorithms forclassifying new work objects. The work object corpus of certainembodiments is limited in applicability to a particular group/team orother grouping of users that may access the work objects. Thus, aplurality of work object corpuses may be stored and isolated from oneanother at the group-based communication platform to maintain privacybetween data exchanged within individual groups/teams. Each work objectcorpus of certain embodiments is subdivided into sub-corpuses for reachwork object type. The database storage areas 108A-108N may utilize anyof a variety of database storage and indexing methodologies, such asthose associated with MySQL, Vitess, and/or the like (which may besharded into discrete data storage areas, to provide additional securityagainst unauthorized/incidental disclosure of information within workobjects to unauthorized individuals). In certain embodiments, theprocessor 202 may provide stored and/or indexed work objects (e.g.,indexed based on key data corresponding to the work objects andassociated database shard to which the message is indexed) to theinterface computing entity 109 for dissemination to client devices101A-101N and/or to platform interface 111 for dissemination to clientdevices 102 via applicable validated external resources 112A-112N. Theprocessor 202 may additionally be configured to maintain a reference(e.g., a data table) for indicating where messages relating toparticular communication channels are stored. Because data may besharded to a plurality of discrete storage locations (e.g., based on achannel identifier), the processor 202 may be configured to direct workobjects to the appropriate storage location once received, and to directwork objects from particular database shards to appropriate clientdevices 101A-101N, 102 to disseminate work objects exchanged within aparticular communication channel.

A database may be embodied as a plurality of physically discretedatabase storage areas 108A-108N (e.g., each database storage area maydefine one or more database shards in certain embodiments). For example,each physical discrete database storage area 108A-108N may have anassociated physical location, an associated unique identifier, and/orthe like. These physically discrete database storage areas 108A-108N maybe configured for operating as a cohesive storage unit that may beaccessed, for example, by one or more operation servers 107A-107N.Moreover, the group-based communication platform 105 may be configuredfor storing related data, such as work objects exchanged in associationwith a common communication channel, within a common discrete datastorage device.

In some embodiments, the apparatus 200 may include input/outputcircuitry 206 that may, in turn, be in communication with processor 202to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 206 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a client device, a kiosk, or the like.In some embodiments, the input/output circuitry 206 may also include akeyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input/output mechanisms. The processorand/or user interface circuitry comprising the processor may beconfigured to control one or more functions of one or more userinterface elements through computer program instructions (e.g., softwareand/or firmware) stored on a memory accessible to the processor (e.g.,memory 204, and/or the like).

The communications circuitry 208 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 200. In this regard, the communications circuitry 208may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications circuitry 208 may include one or morenetwork interface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communications circuitry 208 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

Message amplifier circuitry 210 includes hardware configured to copy andamplify electronic messages (or other work objects) and associatedmetadata received from one or more client devices 101A-101N, 102 toother client devices 101A-101N, 102. The message amplifier circuitry 210may utilize processing circuitry, such as the processor 202, to performthese actions. However, it should also be appreciated that, in someembodiments, the message amplifier circuitry 210 may include a separateprocessor, specially configured Field Programmable Gate Array (FPGA), orApplication Specific Integrated Circuit (ASIC) for performing thefunctions described herein (e.g., for providing messages to variousvalidated external resources, where applicable). The message amplifiercircuitry 210 may be implemented using hardware components of theapparatus configured by either hardware or software for implementingthese planned functions.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 200. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

In the illustrated embodiment of FIG. 3, the interface computing entity109 is embodied by one or more computing systems encompassing apparatus300. The illustrated apparatus 300 includes processor 301, memory 303,input/output circuitry 305, and communications circuitry 307. Theapparatus 300 may be configured to execute the operations describedherein with respect to FIGS. 1-15. Although these components 301-307 aredescribed with respect to functional limitations, it should beunderstood that the particular implementations necessarily include theuse of particular hardware. It should also be understood that certain ofthese components 301-307 may include similar or common hardware. Forexample, two sets of circuitries may both leverage use of the sameprocessor, network interface, storage medium, or the like to performtheir associated functions, such that duplicate hardware is not requiredfor each set of circuitries.

In some embodiments, the processor 301 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 303 via a bus forpassing information among components of the apparatus. The memory 303 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 303 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 303 may be configured to store information, data,content, applications, instructions, or the like for enabling theapparatus 300 to carry out various functions in accordance with exampleembodiments of the present invention. For example, the memory 303 may beconfigured to cache work objects exchanged on one or more group-basedcommunication channels, such that the processor 301 may provide variousmessages to client devices (e.g., on an as needed or as requestedbasis).

In some preferred and non-limiting embodiments, the processor 301 may beconfigured to execute instructions stored in the memory 303 or otherwiseaccessible to the processor 301. In some preferred and non-limitingembodiments, the processor 301 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 301 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 301 is embodied as an executor of software instructions, theinstructions may specifically configure the processor 301 to perform thealgorithms and/or operations described herein when the instructions areexecuted.

In some embodiments, the apparatus 300 may include input/outputcircuitry 305 that may, in turn, be in communication with processor 301to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 305 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a client device, a kiosk, or the like.In some embodiments, the input/output circuitry 305 may also include akeyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input/output mechanisms.

The communications circuitry 307 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 300. In this regard, the communications circuitry 307may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications circuitry 307 may include one or morenetwork interface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communications circuitry 307 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 300. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

Moreover, although the interface computing entity 109 is shown withinthe bounds of the group-based communication platform 105, it should beunderstood that the interface computing entity 109 may be embodied as anedge-based computing device in communication with aspects of thegroup-based communication platform 105 via a communication network 103.Such embodiments may comprise a plurality of interface computingentities 109 that are geographically distributed, and such interfacecomputing entities 109 may be configured for communicating with clientdevices 101A-101N within a geographic range proximate a respectiveinterface computing entity 109.

In the illustrated embodiment of FIG. 4, the platform interface 111 isembodied by one or more computing systems encompassing apparatus 400.The illustrated apparatus 400 includes processor 401, memory 403,input/output circuitry 405, and communications circuitry 407. Theapparatus 400 may be configured to execute the operations describedherein with respect to FIGS. 1-15. Although these components 401-407 aredescribed with respect to functional limitations, it should beunderstood that the particular implementations necessarily include theuse of particular hardware. It should also be understood that certain ofthese components 401-407 may include similar or common hardware. Forexample, two sets of circuitries may both leverage use of the sameprocessor, network interface, storage medium, or the like to performtheir associated functions, such that duplicate hardware is not requiredfor each set of circuitries.

In some embodiments, the processor 401 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 403 via a bus forpassing information among components of the apparatus. The memory 403 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 403 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 403 may be configured to store information, data,content, applications, instructions, or the like for enabling theapparatus 400 to carry out various functions in accordance with exampleembodiments of the present invention. For example, the memory 403 may beconfigured to store access addresses (e.g., URLs) utilized by one ormore validated external resources 112A-112N for sharing work objectsbetween the group-based communication platform 105 and those validatedexternal resources 112A-112N.

In some preferred and non-limiting embodiments, the processor 401 may beconfigured to execute instructions stored in the memory 403 or otherwiseaccessible to the processor 401. In some preferred and non-limitingembodiments, the processor 401 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 401 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 401 is embodied as an executor of software instructions, theinstructions may specifically configure the processor 401 to perform thealgorithms and/or operations described herein when the instructions areexecuted.

In some embodiments, the apparatus 400 may include input/outputcircuitry 405 that may, in turn, be in communication with processor 401to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 405 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a client device, a kiosk, or the like.In some embodiments, the input/output circuitry 405 may also include akeyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input/output mechanisms.

The communications circuitry 407 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 400. In this regard, the communications circuitry 407may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications circuitry 407 may include one or morenetwork interface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communications circuitry 407 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 400. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

Moreover, although the platform interface 111 is shown within the boundsof the group-based communication platform 105, it should be understoodthat the platform interface 111 may be embodied as an edge-basedcomputing device in communication with aspects of the group-basedcommunication platform 105 via a communication network 103. Suchembodiments may comprise a plurality of platform interfaces 111 that aregeographically distributed, and such platform interfaces 111 may beconfigured for communicating with validated external resources 112A-112Nwithin a geographic range proximate a respective platform interface 111.

The term “circuitry” should be understood broadly to include hardwareand, in some embodiments, software for configuring the hardware. Withrespect to components of each apparatus 200, 300, 400, the term“circuitry” as used herein should therefore be understood to includeparticular hardware configured to perform the functions associated withthe particular circuitry as described herein. For example, in someembodiments, “circuitry” may include processing circuitry, storagemedia, network interfaces, input/output devices, and the like. In someembodiments, other elements of the apparatus 200 may provide orsupplement the functionality of particular circuitry. For example, theprocessor 202 may provide processing functionality, the memory 204 mayprovide storage functionality, the communications circuitry 208 mayprovide network interface functionality, and the like Similarly, otherelements of the apparatus 300 may provide or supplement thefunctionality of particular circuitry. For example, the processor 301may provide processing functionality, the memory 303 may provide storagefunctionality, the communications circuitry 307 may provide networkinterface functionality, and the like. Similar concepts may be embodiedwith apparatus 400.

As will be appreciated, any such computer program instructions and/orother type of code may be loaded onto a computer, processor or otherprogrammable apparatus's circuitry to produce a machine, such that thecomputer, processor or other programmable circuitry that execute thecode on the machine creates the means for implementing variousfunctions, including those described herein.

As described above and as will be appreciated based on this disclosure,embodiments of the present invention may be configured as methods,mobile devices, backend network devices, and the like. Accordingly,embodiments may comprise various means including entirely of hardware orany combination of software and hardware. Furthermore, embodiments maytake the form of a computer program product on at least onenon-transitory computer-readable storage medium having computer-readableprogram instructions (e.g., computer software) embodied in the storagemedium. Any suitable computer-readable storage medium may be utilizedincluding non-transitory hard disks, CD-ROMs, flash memory, opticalstorage devices, or magnetic storage devices.

Examples of electronic information exchange among one or more clientdevices 101A-101N, 102 the group-based communication platform 105, andone or more validated external resources 112A-112N are described hereinwith reference to FIG. 1.

As shown in FIG. 1, the group-based communication platform 105 enablesindividual client devices 101A-101N, 102 to exchange work objects withone another via the group-based communication platform 105 and/or viaone or more validated external resources 112A-112N, if necessary. Forclient devices 101A-101N to exchange such work objects, individualclient devices 101A-101N transmit work objects (e.g., messages, emails,files, events, and/or the like) to an interface (e.g., interfacecomputing entity 109) via a communication protocol (e.g., via awebsocket, a non-RTM messaging protocol, and/or the like). Those workobjects are ultimately provided to one or more operation servers107A-107N, which indexes the messages within database storage areas108A-108N and distributes those work objects to the intended recipients(e.g., client devices 101A-101N, 102). The distributed work objects areprovided to the recipient client devices 101A-101N, 102 via theinterface computing entity 109 (or interface entity 111 and one or morevalidated external resources 112A-112N, if applicable), which maintainswebsocket connections with individual recipient client devices 101A-101Nof the work object, and maintains one or more backend connections withthe various operation servers 107A-107N. Work objects may be similarlydistributed from client devices 102, by disseminating those work objectsthrough applicable validated external resources 112A-112N to thegroup-based communication platform 105, which disseminates work objectsin a matter as discussed above.

Work Objects

Work objects may be exchanged among one or more users (via respectiveclient devices 101A-101N, 102) through the group-based communicationplatform 105 and/or one or more validated external resources 112A-112N.Work objects need not be limited to execution via one or more apps(either local or browser based) corresponding to the communicationplatform utilized for exchange. For example, a work object embodied as amessage in accordance with certain embodiments is natively displayed viaapps specifically configured for use with the group-based communicationplatform 105, however these messages may be readable by apps configuredfor use with validated external resources 112A-112N. As a specificexample, the group-based communication platform 105 generates cacheobjects specifically configured for use with one or more validatedexternal resources. Certain work objects however, may be tied to usagewith a particular third party app or a particular type of app (which mayhave direct integration with a communication platform app, or may beaccessible only outside of the communication platform app). For example,work objects embodied as audio files may only be executable via one ormore apps configured for parsing audio files.

In certain embodiments, reading of particular work objects may belimited by encryption methodologies tied into those work objects. Forexample, certain encrypted work objects may only be readable through aspecific app instance operating on and/or in association with aparticular client device 101.

Moreover, as discussed herein, the operation servers 107A-107N may beconfigured for establishing one or more cache objects to be disseminatedas a representation of an underlying work object. Such cache objects mayprovide preliminary data regarding the work object in a format that iseasily and quickly rendered at a client device 101A-101N, 102. Thus, auser may determine whether additional information is needed regardingthe underlying work object that justifies requesting the entirety of theunderlying work object from an indexed storage location. In certainembodiments, the configuration of these cache objects is determinedbased at least in part on the work object type, an associated validatedexternal resource (if any), and/or the like, as discussed herein.

Although the final representation of a cache object may be at leastpartially dependent on the type of work object represented, these cacheobjects may be generated utilizing a common cache object template,providing varying levels of detail for display regarding a particularwork object. The cache object templates may be general, such that thetemplates are applicable to all (or at least a plurality of) work objecttypes, or the cache object templates may be specific to particular workobject types (both for summary cache objects and expanded cache objects,both of which are discussed herein), may provide an icon area(configured for displaying an icon indicative of the type of work objectrepresented by the cache object, a source area (e.g., configured toprovide data indicative of a source of a particular work object, such asvia email, via message, via external application, and/or the like), awork object name area, a date and time area (e.g., a date and time ofgeneration, a date and time of the occurrence of an event underlying aparticular work object, and/or the like), a duration area (e.g., forevents), a creator area, an other people/users area (e.g., invitees,intended recipients, and/or the like), content of the work object area(e.g., a short summary, a short clip, the entirety of the work object,and/or the like), an action area comprising one or more actionsavailable for the work object (e.g., providing attendance data forevents, answering a call, ending a call, replying to an email, and/orthe like), an attachment area (e.g., providing an indication ofattachments provided with a work object), and/or the like.

Moreover, cache objects may be provided at various levels of detail, andinteraction with a cache object may cause a client device 101A-101N toretrieve and display a more detailed cache object relating to the sameunderlying work object. For example, cache objects may encompass summarycache objects (also referred to herein as first-level cache objects)providing extremely basic details regarding a work object, designed toenable a user to identify what the work object is (e.g., an email with aparticular subject line, a file with a particular file name, and/or thelike). In certain embodiments, the summary cache objects may encompass alimited quantity of content of the underlying work object (e.g., thefirst 2-4 lines of an email) to provide additional context for the user.The summary cache objects may be displayed via a client device 101A-101Nwithin a visual container corresponding to a particular cache object.Moreover, as discussed herein, these summary cache objects may be passedto the client device 101A-101N for local storage and caching inreal-time. In various embodiments, the underlying work object may beretained for storage at the group-based communication platform 105(e.g., within one or more database storage areas 108).

The cache objects may further encompass expanded cache objects (alsoreferred to herein as second-level cache objects). These expanded cacheobjects provide detailed content data from the underlying work object,however these expanded cache objects may omit formatting or othermetadata of the underlying work objects. These expanded cache objectsmay be accessed by interacting (e.g., clicking) on a summary cacheobject displayed to a user via a client device 101A-101N. The expandedcache objects may be configured for display in a separate display window(e.g., a pop-up interface), or the expanded cache objects may visuallyunfurl for display in-line with messages and/or other work objectsexchanged and displayed in the same display, for example, via mechanismsand processes as discussed in co-pending U.S. patent application Ser.No. 15/655,981, filed Jul. 21, 2017, the contents of which areincorporated herein by reference in their entirety.

In various embodiments, the expanded cache objects may be stored at thegroup-based communication platform 105, and may be retrieved andtransmitted to a requesting client device 101 only upon receipt of anindication that a user interacted with a related summary cache object atthe client device 101. In other embodiments, the expanded cache-objectsmay be provided to the client devices 101A-101N in real-time, howeverthe expanded cache objects may not be displayed to a user until andunless the user interacts with the related summary cache object.

Moreover, in embodiments in which work objects are shared with clientdevices 102 via one or more validated external resources 112A-112N, boththe summary cache object and the expanded cache object corresponding toa particular work object may be passed to the client devices 102 inreal-time (or according to other defined work object transmissionprotocol). The cache object passed to client device 101A-101N and tovalidated external resources may be identical, or separate cache objectsmay be generated for distribution to the client devices 101A-101N andeach of the validated external resources. For example, formatting dataand/or other configuration data of cache objects may be speciallydefined for operating with various validated external resources. In suchembodiments, the summary cache object may be presented to the clientdevice 102 as a portion of a transmission (e.g., within the body of anemail message), and the expanded cache object may be presented to theuser as an attachment to the transmission (e.g., a separate fileattachment). In other embodiments, the full work object (discussedbelow) may be attached to the transmission instead of the expanded cacheobject. Alternatively, the summary cache object may be an interactivehyperlink, which directs a client device 102 to a URL that causes theclient device 102 to display (e.g., via a browser) or download theexpanded cache object and/or the full work object.

In certain embodiments, the full work object may be accessed by a clientdevice 101A-101N by interacting with the expanded cache object. Such aninteraction at the client device 101A-101N may cause the client deviceto generate and transmit a request to the group-based communicationplatform 105 to provide the full work object to the client device101A-101N (including formatting and/or any other underlying metadata).In certain embodiments, providing the full work object to the clientdevice 101A-101N may cause the client device 101A-101N to initiate anexternal application operating on the client device 101A-101N fornatively displaying the work object (e.g., an email may cause the clientdevice 101A-101N to display the email work object within an email viewerapplication; a video file may cause the client device 101A-101N toinitialize a video player application such that the video file executesvia the video play application; and/or the like). Similar configurationsmay be provided for work objects provided to client devices 102accessing the work objects via one or more validated external resources112A-112N.

In yet other embodiments, full work objects may be displayable withinobject-specific containers either in-line or within modals of thegroup-based communication interface. These modals of certain embodimentsprovide an area within a display of a client device for displaying theentirety of the work object. When a work object is accessed from withinthe group-based communication interface (at client devices 101A-101N),the modals occur within the group-based communication interface. Thus,users seeking to view a full work object need not open a separateapplication or to be directed outside of the group-based communicationinterface to view full work objects. It should be understood that suchfunctionality for viewing full work objects within the group-basedinterface may be provided for all work objects in certain embodiments,or may be provided for only a subset of work objects for which thegroup-based communication interface is capable of executing, reading, orusing the work object. In such embodiments, the receiving client device101A-101N need not initialize a separate application for viewing thework object. In certain embodiments, modals or other containers may beprovided for executing an instance of an external application (e.g., afull version of an external application or a limited version of anexternal application) within the displayed modal, such that other workobjects may be displayed within the group-based communication interface,even while accessing executable portions of an external application.

Moreover, upon a client device 101A-101N requesting a full work object,the client device 101A-101N may be configured to locally store the workobject thereon for later access without a network connection. In otherembodiments, the client device 101A-101N may be configured to store thefull work object in short-term cache memory for display during thecurrent interaction session, and may thereafter remove the work objectfrom local memory once the user is no longer interacting with the workobject. In the latter embodiments, later requests to access the fullwork object would be fulfilled by again transmitting the full workobject to the client device 101A-101N from the group-based communicationplatform 105 in response to an access request generated at the clientdevice 101A-101N.

Messages

In some embodiments of an exemplary group-based communication platform105, a message, messaging communication, or other internal work objectmay be sent from a client device 101A-101N to a group-basedcommunication platform 105. In various implementations, messages may besent to the group-based communication platform 105 over communicationnetwork 103 directly by one of the client devices 101A-101N. Themessages may be sent to the group-based communication platform 105 viaan intermediary. For example, a client device 101A-101N may be adesktop, a laptop, a tablet, a smartphone, and/or the like that isexecuting a client application (e.g., a group-based communication app).In one implementation, the message may include data such as a messageidentifier, sending user identifier, a group identifier, a group-basedcommunication channel identifier, message contents (e.g., text, emojis,images, links), attachments (e.g., files or other work objects), messagehierarchy data (e.g., the message may be a reply to another message),third party metadata, and/or the like. In one embodiment, the clientdevice 101A-101N may provide the following example message,substantially in the form of a (Secure) Hypertext Transfer Protocol(“HTTP(S)”) POST message including eXtensible Markup Language (“XML”)formatted data, as provided below:

POST /authrequest.php HTTP/1.1 Host: www.server.com Content-Type:Application/XML Content-Length: 667 <?XML version = “1.0” encoding =“UTF-8”?> <auth_request> <timestamp>2020-12-31 23:59:59</timestamp><user_accounts_details> <user_account_credentials><user_name>ID_user_1</user_name> <password>abc123</password> //OPTIONAL<cookie>cookieID</cookie> //OPTIONAL<digital_cert_link>www.mydigitalcertificate.com/JohnDoeDaDoeDoe@gmail.com/mycertifcate.dc</digital_cert_link> //OPTIONAL<digital_certificate>_DATA_</digital_certificate></user_account_credentials> </user_accounts_details> <client_details>//iOS Client with App and Webkit //it should be noted that althoughseveral client details //sections are provided to show example variantsof client //sources, further messages will include only on to save//space <client_IP>10.0.0.123</client_IP> <user_agent_string>Mozilla/5.0(iPhone; CPU iPhone OS 7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML,like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53</user_agent_string><client_product_type>iPhone6,1</client_product_type><client_serial_number>DNXXX1X1XXXX</client_serial_number><client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_UDID><client_OS>iOS</client_OS> <client_OS_version>7.1.1</client_OS_version><client_app_type>app with webkit</client_app_type><app_installed_flag>true</app_installed_flag><app_name>MSM.app</app_name> <app_version>1.0 </app_version><app_webkit_name>Mobile Safari</client_webkit_name><client_version>537.51.2</client_version> </client_details><client_details> //iOS Client with Webbrowser<client_IP>10.0.0.123</client_IP> <user_agent_string>Mozilla/5.0(iPhone; CPU iPhone OS 7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML,like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53</user_agent_string><client_product_type>iPhone6,1</client_product_type><client_serial_number>DNXXX1X1XXXX</client_serial_number><client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_UDID><client_OS>iOS</client_OS> <client_OS_version>7.1.1</client_OS_version><client_app_type>web browser</client_app_type> <client_name>MobileSafari</client_name> <client_version>9537.53</client_version></client_details> <client_details> //Android Client with Webbrowser<client_IP>10.0.0.123</client_IP> <user_agent_string>Mozilla/5.0 (Linux;U; Android 4.0.4; en-us; Nexus S Build/IMM76D) AppleWebKit/534.30(KHTML, like Gecko) Version/4.0 Mobile Safari/534.30</user_agent_string><client_product_type>Nexus S</client_product_type><client_serial_number>YXXXXXXXXZ</client_serial_number><client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX- XXXXXXXXXXXXX</client_UDID><client_OS>Android</client_OS><client_OS_version>4.0.4</client_OS_version> <client_app_type>webbrowser</client_app_type> <client_name>Mobile Safari</client_name><client_version>534.30</client_version> </client_details><client_details> //Mac Desktop with Webbrowser<client_IP>10.0.0.123</client_IP> <user_agent_string>Mozilla/5.0(Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.75.14 (KHTML, likeGecko) Version/7.0.3 Safari/537.75.14</user_agent_string><client_product_type>MacPro5,1</client_product_type><client_serial_number>YXXXXXXXXZ</client_serial_number><client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX- XXXXXXXXXXXXX</client_UDID><client_OS>Mac OS X</client_OS><client_OS_version>10.9.3</client_OS_version> <client_app_type>webbrowser</client_app_type> <client_name>Mobile Safari</client_name><client_version>537.75.14</client_version> </client_details> <message><message_identifier>ID_message_10</message_identifier><team_identifier>ID_team_1</team_identifier><channel_identifier>ID_channel_1</channel_identifier> <contents>That isan interesting invention. I have attached a copy our patentpolicy.</contents> <attachments>patent_policy.pdf</attachments></message> </auth_request>

In the illustrated embodiment, the group-based communication platform105 comprises a plurality of operation servers 107A-107N configured toreceive and/or disseminate messages transmitted between and/or to aplurality of client devices 101A-101N within a channel identified by achannel identifier and/or a group identifier; to facilitate indexing ofthose messages as discussed herein; and/or to facilitate disseminationof those messages among client devices 101A-101N that collectively formthe membership of the communication channel and client devices 102having access to work objects shared within the communication channelvia one or more validated external resources 112A-112N.

In some embodiments, data indicating responses may be associated with amessage. For example, responses to the message by other users mayinclude reactions (e.g., selection of an emoji associated with themessage, selection of a “like” button associated with the message),clicking on a hyperlink embedded in the message, replying to the message(e.g., posting a message to the communication channel interface inresponse to the message), downloading a file associated with themessage, sharing the message from one group-based communication channelto another group-based communication channel, pinning the message,starring the message, and/or the like. In one implementation, dataregarding responses to the message by other users may be included withthe message, and the message may be parsed (e.g., using PHP commands) todetermine the responses. In another implementation, data regardingresponses to the message may be retrieved from a database. For example,data regarding responses to the message may be retrieved via a Vitessdatabase command, or a MySQL database command similar to the following:

-   -   SELECT messageResponses    -   FROM MSM_Message    -   WHERE messageID=ID_message_10.

For example, data regarding responses to the message may be used todetermine context for the message (e.g., a social score for the messagefrom the perspective of some user). In another example, data regardingresponses to the message may be analyzed to determine context regardingthe user (e.g., the user's expertise in a topic may be determined basedon the responses to the user's message regarding the topic, and theuser's expertise may be assigned to the user identifier).

In embodiments, attachments may be included with the message. Theseattachments may, in certain circumstances, constitute separate workobjects (e.g., files, event invitations, and/or the like), which may bereceived and processed by the operation servers 107A-107N in accordancewith their respective work object type. In one implementation, themessage may be parsed (e.g., using PHP commands) to determine file namesof the attachments. For example, file contents may be analyzed todetermine context for the message (e.g., a patent policy document mayindicate that the message is associated with the topic “patents”).

In embodiments, a conversation primitive may be associated with themessage. In one implementation, a conversation primitive is an elementused to analyze, index, store, and/or the like messages and/or otherwork objects. For example, the message may be analyzed by itself, andmay form its own conversation primitive. In another example, the messagemay be analyzed along with other messages that make up a conversation(e.g., together with other relevant work objects), and the messages thatmake up the conversation may form a conversation primitive. In oneimplementation, the conversation primitive may be determined as themessage, a specified number (e.g., two) of preceding messages and aspecified number (e.g., two) of following messages. In anotherimplementation, the conversation primitive may be determined based onanalysis of topics discussed in the message and other messages (e.g., inthe channel) and/or proximity (e.g., message send order proximity,message send time proximity) of these messages relative to one anotherand/or relative to other work objects.

As discussed herein, work object context data, such as metadata and/orthe contents of the message may be used to index the message (e.g.,using the conversation primitive), to facilitate various facets ofsearching (i.e., search queries that return results from the operationservers 107A-107N), and/or to otherwise establish one or morerelationships with other work objects (e.g., other messages or otherwork objects). Metadata associated with the message may be determinedand the message may be indexed in the database storage areas 108A-108N.In one embodiment, the message may be indexed such that messages sharedwithin a particular communication channel are stored separately. In oneimplementation, messages may be indexed at a plurality of separatedistributed repositories (e.g., to facilitate scalability). If there areattachments associated with the message, file contents of the associatedfiles may be used to index such files and messages in the operationservers 107A-107N to facilitate searching.

Message Intake and Distribution

Messages are generated by and received from client devices 101A-101Ninteracting directly with the group-based communication platform 105.FIG. 5 illustrates various processes performed by various computingentities discussed herein with respect to message intake anddistribution. As mentioned, messages are initially generated at clientdevices 101A-101N, as shown at Block 501. Messages are generated inresponse to user input received at the generating client device101A-101N, and are indicative of the content the user intended to conveyto others by way of the generated message (e.g., the user may provideuser input of “Howdy Group!” to be conveyed to others via the message).As should be understood, messages may contain alphanumeric text, emojis,and/or other input provided by the user. The content generated by theuser (e.g., via user input) is combined with other context datagenerated by and/or relating to the client device 101A-101N andapplicable to the message. This context data comprises metadata (asreflected in the sample message above) to enable the message to beappropriately parsed and disseminated via the group-based communicationplatform 105. As discussed in greater detail herein, users may alsoattach other work objects (e.g., files) to messages as well.

The generated messages are passed to the group-based communicationplatform 105, specifically to one or more of the operation servers107A-107N, via the interface computing entity 109. The operation servers107A-107N receive the generated message (as shown at Block 502) andprepare the message for distribution to the appropriate recipients ofthe message. The operation servers 107A-107N determine appropriaterecipients of the message (e.g., other users of the group-basedcommunication platform 105 that are accessible via message-baseddistribution and/or other potential recipients that are accessible viavalidated external resources 112A-112N) by parsing the message metadata,as indicated at Block 503. As discussed above, the message metadata maybe indicative of a group-based communication channel in which themessage is to be exchanged. As discussed, the channel may have one ormore other members, which may be determined to be intended recipients ofthe message. Moreover, the channel data may indicate that messages arealso to be disseminated to users outside of the group-basedcommunication platform 105. As a specific example, data associated withthe channel may indicate that a particular email address is designatedto receive messages exchanged within the group-based communicationchannel. Based on the parsed metadata, the operation servers 107A-107Ndetermine the appropriate route of dissemination of the message (e.g.,via one or more existing communication channels and/or one or moreinter-system communication pathways). In certain embodiments, thegroup-based communication platform 105 determines the most appropriateprocess for distribution based at least in part on the validatedexternal resource to be utilized for communication of the message to oneor more client devices 102.

Moreover, in certain embodiments, the operation servers 107A-107N maypass the message to one or more database storage areas 108A-108N forindexing. The databases may generate and append supplemental metadata tothe message after review of the context data, as indicated at Block 504.Such supplemental metadata may comprise metadata indicative of a topicassigned to the message. Moreover, such supplemental metadata may begenerated in accordance with one or more artificial intelligence and/ormachine-learning algorithms configured to review the context data, suchas the substantive contents of the message and/or the metadataassociated with the message to determine an appropriate topic to beassigned to the message. In certain embodiments, the topics availablefor assignment may be established manually by user input, and thedatabase storage areas 108A-108N may be configured to select amost-appropriate topic (or multiple topics) from the establishedlisting. In other embodiments, the artificial intelligence and/ormachine learning algorithms may be configured for automaticallygenerating a topic in instances in which previously generated topics aredeemed too tenuous for description of the message.

As a specific example, the database storage areas 108A-108N may utilizecontext data of the message, such as the message content (which may bereviewed utilizing a term-frequency, inverse document frequency (Tf-idf)algorithm in light of a larger dataset of messages to identify relevanttopics), message metadata (e.g., reviewing topics assigned to threads inwhich the message is a part. The databases may also and/or alternativelyidentify a sending user identifier and determine the sending useridentifier's assigned subject matter expertise to weigh the potentialtopics that may be assigned to the message), and/or the like todetermine an appropriate topic.

Ultimately, the database storage areas 108A-108N index the message, asshown at Block 505, which may make the message available for latersearch/retrieval (e.g., for queries satisfying message accessrequirements, such as meeting authorization prerequisites to view themessage (e.g., a private message may be searchable by the sender andreceiver, but no one else)).

The operation servers 107A-107N disseminate the message to intendedrecipients (e.g., the originally received message or the indexed messageincluding the supplemental metadata) as shown at Block 506. Recipientclient devices 101A-101N accessible directly via the group-basedcommunication platform may receive messages via distribution through theinterface computing entity 109 (as indicated by Block 507) and mayrender those messages (e.g., using style guides stored locally on thoseclient devices 101A-101N) as indicated at Block 508.

To disseminate messages (or other internal work objects) to other usersutilizing client devices 102 to access data provided via one or morevalidated external resources, the operation servers 107A-107N determineappropriate validated external resources to be utilized for messagedissemination. Those validated external resources may be identifiedbased at least in part on data identifying intended recipients (e.g.,validated external resource identifiers). Based at least in part on theidentified validated external resources to receive the messages, theoperation servers 107A-107N construct work object data and/or cacheobjects that may be usable by the validated external resources and/orclient devices configured for operating in conjunction with theidentified validated external resources. Recipients reachable via one ormore validated external resources 112A-112N may receive messagesdisseminated from the group-based communication platform 105 by receiptat the applicable validated external resource 112A-112N (as indicated atBlock 509), which may then disseminate the message to client devices 102(e.g., with an appropriate style guide applicable to work objects commonto the validated external resource 112A-112N). The client device 102 maythen receive the message and render the message for display, asindicated at Blocks 510-511.

Because the validated external resources 112A-112N may utilize separatestyle guides for work object display, the group-based communicationplatform 105 may be configured to transmit the messages to the validatedexternal resources 112A-112N via one or more formatting agnostic datatransmission protocols. For example, the group-based communicationplatform 105 may pass message data to validated external resources112A-112N via one or more APIs, via one or more proxy endpointsproviding message data in a format discernable to the validated externalresource 112A-112N to automatically identify various components of themessage data (e.g., XML formatting providing various labeled containersof data), and/or the like. The validated external resource 112A-112N maythen apply self-imposed formatting guides to the messages and/or mayautomatically omit various portions of the message data, as needed tocomply with the self-imposed formatting.

Emails

Emails are a type of external work object for exchanging data betweenmultiple client device 102 users. Emails may contain alphanumeric textonly (ASCII format emails) or additional data contents (e.g.,Multipurpose Internet Mail Extensions (MIME) format, rich text format,and/or the like), such as data indicative of desired formatting of text,various work objects included as attachments, and/or the like. Emailsmay be disseminated in accordance with included email addresses, whichare indicative of a domain of a user (e.g., a recipient's domain or asending user's domain)—thereby providing email systems with sufficientdata to direct the email to the appropriate domain system (e.g., whichmay be a type of validated external resource 112 as discussed herein);and a local portion—thereby providing the domain with sufficientinformation to identify the user associated with the message (e.g., theintended recipient or the sending user). Thus, an entire email addressprovides sufficient data to direct email work objects between users.

Emails may comprise context data, such as content data indicative of thecontent a user desires to provide to another user, and metadataindicative of various characteristics of the email. Context data ofemails is generally different (e.g., in content and/or formatting) thancontext data of messages and other internal work objects and may varybetween email systems utilized to generate the emails. For example,certain metadata may be unique to particular sending email systems.Metadata such as the sending user email address, the recipient(s) useremail address(es), the sent time/date, the received time/data, emailsize, email subject, whether the email is flagged as private/public,whether the email is flagged as important/low importance/and/or thelike; or other characteristics of the email may be reflected within themetadata. Moreover, metadata associated with the email may be indicativeof the type of formatting applied to the email (which, as discussedherein, may be utilized later for formatting other work objectsgenerated based on the email).

Emails may be generated at client devices 102, and disseminationtherefrom may pass through one or more validated external resources112A-112N (including, for example, a domain host computing entity of thesending user identifier and one or more domain host computing entitiesof the recipient(s) of the email). As discussed herein, the group-basedcommunication platform 105 may be configured to operate as a recipientand/or a sending domain host for emails to enable inter-platformcommunication therewith.

Email Intake and Dissemination

As discussed above, emails may be provided to the group-basedcommunication platform 105 from one or more validated external resources112A-112N. Emails are provided via a defined communication pathwayleading to/through the group-based communication platform 105, such as acommunication pathway established specifically for providing emails tothe group-based communication platform 105. In certain embodiments, thegroup-based communication platform 105 may be configured to generateand/or host one or more email addresses to act as recipients for emailsgenerated via the one or more validated external resources 112A-112N.These email addresses hosted by the group-based communication platform105 may be channel email addresses, wherein each group-basedcommunication channel is assigned (either automatically or manually) achannel email address such that emails directed to the channel emailaddress may be disseminated to members of the channel, for example, as apart of a communication interface provided to client devices 101A-101Nhaving access to the channel via the group-based communication platform105. As just one example, upon generation of a channel (or aftergeneration of a channel and in response to a trigger event, such as auser request) the group-based communication platform 105 mayautomatically generate an email address to be assigned to the channel.The email address may comprise a randomly assigned string ofalphanumeric characters representing the local portion of the emailaddress, and may be hosted at a defined domain corresponding to thegroup-based communication platform 105. As an example, an email addressassigned to a particular channel may be “w94kxetuu4234dkfr@slack.com.”

In other embodiments, the local portion of the email address may beindicative of the identity of the channel and/or group to which it isassigned. For example, an email address for Company Corp's channelentitled “fat cats” may be embodied as“fat_cats.company_corp@slack.com.” It should be understood that otherformats and/or domains may be provided/utilized.

In other embodiments, a general email address or other communicationpathway (not specific to any one communication channel) may be utilizedand context data of emails may be utilized to direct the email toparticular intended recipients and/or to a particular communicationchannel.

Once received at the group-based communication platform 105, emails maybe processed for indexing/storage and for dissemination to any otheridentified intended recipients not otherwise provided for with theinitial email transmission. FIG. 6 illustrates an example process forintake processing of emails into the group-based communication platform105. As shown at Block 601 a client device 102 generates an email to bedisseminated to one or more users. The email is sent to a validatedexternal resource 112A-112N (e.g., a sending user domain), whichreceives the email, as indicated at 602, and may forward the email alongto a separate validated external resource 112A-112N (e.g., a recipientdomain validated external resource, not separately shown in FIG. 6), asa part of disseminating the email to intended recipients and asindicated at Block 603. Emails transmitted to other email recipients arethen provided to client devices 102, as indicated at Block 604, whichrender the emails for digestion by the user, as indicated at Block 605.

As indicted at Block 606, the email may be further disseminated to thegroup-based communication platform 105 (e.g., by sending the email to anemail address associated with a particular group-based communicationchannel). The group-based communication platform 105 (e.g., via theoperation servers 107A-107N) first identifies what type of work objectis received (e.g., based at least in part on the communication pathwayutilized to receive the work object, and/or other characteristics of thework object). The type of work object received is utilized to determinehow to parse the received work object, as different parsing methods areutilized to extract relevant data within different work object types.The group-based communication platform 105 then parses the context dataof the email, as indicated at Block 607, and provides the email to thedatabase storage areas 108A-108N. While parsing the email, the operationservers 107A-107N identifies content of the email, and may identify oneor more other characteristics of the email that may be integrated withthe messaging configuration of the group-based communication platform105. For example, the operation servers 107A-107N may identifyformatting data for the email, and the operation servers 107A-107N mayascertain appropriate formatting corollaries for the group-basedcommunication platform 105 (which may utilize a unique style guide formessages). Such identified characteristics may be utilized whendisseminating the email to client devices 101A-101N as a part of thegroup-based communication platform (e.g., as summary cache objectsdiscussed herein).

While parsing the email, the group-based communication platform 105retrieves the substantive content of the email (e.g., portions of theemail generated manually by the sending user), which may be utilized forsearching and/or classification of the email. Moreover, the group-basedcommunication platform 105 parses various portions of the metadataincluded with the email to identify relevant characteristics of theemail usable for indexing the email, for classifying the email, and/orotherwise for providing the email to various intended recipients. Forexample, characteristics unique to emails may inform how to combinenewly received emails with previously received emails, and/or forestablishing appropriate topics for newly received emails.

In certain embodiments, the group-based communication platform 105identifies a sender of an email by parsing the metadata received withthe email. The sender may be identified by a sending email address. Thegroup-based communication platform may then determine whether the sendermatches any profiles or other user-identifying data stored at thegroup-based communication platform 105 (e.g., stored within databases108A-108N). Determining whether the sender matches existing userprofiles may be utilized to identify a sender's expertise, which may berelevant for establishing appropriate topics for the email.

Moreover, the group-based communication platform 105 identifies intendedrecipients of the email. The intended recipients may be identified asmembers of a particular communication channel identified as an intendedrecipient and/or as other email addresses identified as intendedrecipients of the email. In certain embodiments, the group-basedcommunication platform 105 is configured to cross-reference specificallyenumerated intended recipients (e.g., identified by email address)against intended recipients within a particular communication channel toidentify duplicate recipients. As noted above in identifying whether asending user matches any user profiles within the group-basedcommunication platform 105, the group-based communication platform 105determines whether any intended recipient email addresses match userprofiles known to the group-based communication platform 105. If aparticular intended recipient is identified as matching a known userprofile, the group-based communication platform 105 determines whetherthe known user profile is reflected as a member of a communicationchannel also indicated as an intended recipient of the email. If a matchis identified, the group-based communication platform 105 determines theemail address is a duplicate. The group-based communication platform 105may then take one or more remedial measures upon identifying a duplicaterecipient, such as delivering the email (as a message) to the user'sgroup-based communication interface without denoting the work object as“new.” In other embodiments, the group-based communication platform 105does not take any remedial actions.

The group-based communication platform 105 may further parse thereceived email to determine whether the email is directly related to anyother existing emails. For example, the group-based communicationplatform 105 may determine whether the email is a part of an emailthread (e.g., whether the email is sent in response to another existingemail). If the group-based communication platform 105 determines thatthe newly received email is associated with an existing email thread,the group-based communication platform 105 may be configured toassociate the email with the previously existing email, such thatgraphical display of the newly received email (e.g., at client devices101A-101N) places the email in a container generated for the previouslyexisting and related email. The container may be flagged as containing anew email for the user. However, if the email is not identified asrelated to an existing email, the group-based communication platform 105may be configured to generate entirely new work object and/or cacheobject data for generating a new cache object for display at group-basedcommunication interfaces of client devices 101A-101N.

The group-based communication platform 105 may further determine whetherthere are any security and/or sharing concerns applicable to the emailwhile parsing the same. The group-based communication platform 105determines what client devices 101A-101N, users, groups, and/or the likemay access the email, which may dictate how the email is utilized and/orindexed (e.g., the security and/or sharing determination may establishwhich work object corpus the email is to be added to).

Moreover, the group-based communication platform may determine whetherany other characteristics exist that are unique to the email. Forexample, particular email source hosts (e.g., hosts associated with thesender) may provide specific metadata content in emails that may beutilized by the group-based communication platform 105 in establishingsupplemental metadata for the email (as discussed herein). For example,specific formatting data may be utilized for identifying appropriateformatting corollaries for use with the cache objects.

As yet another example, while parsing the email, the operation servers107A-107N may determine whether the email is a reply to or is otherwiserelated to an already existing message reflected within the databases108A-108N. The group-based communication platform 105 may be configuredto support email threading, such that identification of an email asbeing related to an already existing email may cause the group-basedcommunication platform 105 to append the newly received email onto anexisting email reflected within the databases 108A-108N Similarly,rather than rendering the newly received email as an entirely separatenew email work object, upon passing the newly received email to one ormore client devices 101A-101N for rendering thereon (as discussed ingreater detail herein), the email may be passed with an indication ofrelation to an existing, previously displayed email message. The clientdevices 101A-101N may then simply append the newly received email to anexisting email work object displayed at the client devices 101A-101N. Incertain embodiments, a summary cache object relating to the emailmessage may be highlighted (e.g., with a flag or other indicator) toreflect the receipt of a new email message), however a new summary cacheobject need not be generated for display relating to the newly receivedemail work object. However, if an email is determined to not be in replyto any existing email, the new email may be disseminated for display asa new work object (e.g., with a corresponding new summary cache object)as discussed herein.

Moreover, while parsing the email, the operation servers 107A-107N maygenerate a lightweight summary cache object representative of the emailfor rendering within visual containers by client devices 101A-101N thatultimately receive the email as a work-object via the group-basedcommunication platform 105. The summary cache object may be constructedfrom portions of the context data of the email, which may be insertedinto a summary cache object template. Other portions of the template maybe selected and/or populated with data generated by the group-basedcommunication platform 105. The summary cache object may comprise atleast a portion of the content of the email (e.g., the title, the firstdefined number of lines, words, characters, and/or the like). In certainembodiments, the summary cache object may omit formatting data, and mayinstead rely on local formatting mechanisms stored locally on the clientdevices 101A-101N for rendering the summary cache object. Examples ofsuch email summary cache objects as may be displayed via a client device101A-101N are shown at FIGS. 7A-7B.

Moreover, the operation servers 107A-107N may generate an expanded cacheobject having additional detail of the email (e.g., the entirety of theemail content), certain formatting characteristics, attachments, and/orthe like) to be associated with the email and the summary cache object.The summary cache object may then be configured to be interactive forthe receiving client devices 101A-101N, such that clicking/selecting thesummary cache object may cause the client device 101A-101N to requestthe expanded cache object from the group-based communication platform105. Likewise, the expanded cache object may be similarly interactive,and clicking/selecting the expanded cache object may cause the clientdevice 101A-101N to request the full email from the group-basedcommunication platform 105.

The databases may generate and append supplemental metadata to the emailafter review of the same, as indicated at Block 608. Such supplementalmetadata may comprise metadata indicative of a topic assigned to theemail. Moreover, such supplemental metadata may be generated inaccordance with one or more artificial intelligence and/ormachine-learning algorithms configured to review the context data, suchas the substantive contents of the email and/or the metadata associatedwith the email to determine an appropriate topic to be assigned to theemail. Certain emails from particular host systems may already include acorollary to topic data (e.g., email labels), which may be utilized as afactor in assigning a topic to the email work object. In certainembodiments, the topics available for assignment may be establishedmanually by user input, and the database storage areas 108A-108N may beconfigured to select a most-appropriate topic (or multiple topics) fromthe established listing. In other embodiments, the artificialintelligence and/or machine learning algorithms may be configured forautomatically generating a topic in instances in which previouslygenerated topics are deemed too tenuous for description of the email.

As a specific example, the database storage areas 108A-108N may utilizecontext data of the email, such as the email content (which may bereviewed utilizing a Tf-idf algorithm in light of a larger dataset ofwork objects to identify relevant topics), email metadata (e.g.,reviewing topics assigned to threads in which the email is a part;identifying a sending user and determining the sending user's assignedsubject matter expertise to weigh the potential topics that may beassigned to the email), and/or the like to determine an appropriatetopic.

Ultimately, the database storage areas 108A-108N index the email, asshown at Block 609, which may make the email available for latersearch/retrieval (e.g., for queries satisfying email accessrequirements, such as meeting authorization prerequisites to view themessage).

In certain embodiments, the operation servers 107A-107N may disseminatethe email (e.g., as a summary cache object) to intended recipients, asindicated at Block 610. In various embodiments, the group-basedcommunication platform may disseminate the summary cache object toclient devices 101A-101N. Those client devices 101A-101N may receive theemail (e.g., the lightweight summary cache work object), as indicated atBlock 611, and may render the email for display, as indicated at Block612. Rendering the email (e.g., the lightweight summary cache workobject may comprise rendering the email to appear as a native workobject of the group-based communication platform). Such renders mayappear as objects disseminated to the user, which may provide certaindata regarding the work object for the user of the client device101A-101N. In certain embodiments, emails may be rendered at the clientdevices 101A-101N with one or more additional action-related buttonsthat may be utilized to further interact with the emails. For example, auser may be provided with options to reply, reply-all, forward, and/orthe like the email from within a group-based communication interface.

To disseminate emails to other users utilizing client devices 102 toaccess data provided via one or more validated external resources, theoperation servers 107A-107N determine appropriate validated externalresources to be utilized for email dissemination. Those validatedexternal resources may be identified based at least in part on dataidentifying intended recipients (e.g., validated external resourceidentifiers). Based at least in part on the identified validatedexternal resources to receive the emails, the operation servers107A-107N construct work object data and/or cache objects that may beusable by the validated external resources and/or client devicesconfigured for operating in conjunction with the identified validatedexternal resources. Moreover, the operation servers 107A-107Ndisseminate the email (e.g., as a summary cache object, as the fullemail, and/or the like) to intended recipients accessing thecommunication exchange via validated external resources 112A-112N asshown at Blocks 613-615. However, it should be understood that thegroup-based communication platform 105 may be configured to recognizewhether intended recipients were included within the recipient list ofthe original email (as determined based on the email metadata), and thegroup-based communication platform 105 may refrain from sendingcontent-duplicate emails to those recipients who have already received aparticular email. In the specific circumstances of the group-basedcommunication platform 105 transmitting the email to validated externalresources via email-based communication pathways, the group-basedcommunication platform 105 may utilize formatting data originallyprovided with the received email to send the email along to recipientvalidated external resources, thereby effectively forwarding the email(e.g., together with any supplemental metadata generated for the email)to the intended recipients.

Recipients reachable via one or more validated external resources112A-112N may receive emails disseminated from the group-basedcommunication platform 105 by receipt at the applicable validatedexternal resource 112A-112N (as indicated at Block 613), which may thendisseminate the emails to client devices 102 (e.g., with an appropriatestyle guide applicable to work objects common to the validated externalresource 112A-112N). The client device 102 may then receive the emailand render the email for display, as indicated at Blocks 614-615.

Because the validated external resources 112A-112N may utilize separatestyle guides for work object display, the group-based communicationplatform 105 may be configured to transmit the emails to the validatedexternal resources 112A-112N via one or more formatting agnostic datatransmission protocols. For example, the group-based communicationplatform 105 may pass email data to validated external resources112A-112N via one or more APIs, via one or more proxy endpointsproviding email data in a format discernable to the validated externalresource 112A-112N to automatically identify various components of theemail data (e.g., XML formatting providing various labeled containers ofdata), and/or the like. The validated external resource 112A-112N maythen apply self-imposed formatting guides to the emails and/or mayautomatically omit various portions of the email data, as needed tocomply with the self-imposed formatting.

Events

Events, event occurrences, or event objects may constitute one of aplurality of work object types (internal work objects and/or externalwork objects) having scheduling parameters, including, for example,calls (e.g., audio calls, video calls, and/or the like), appointments(which may be single-user appointments or multi-user meetings),reminders, dated tasks, objects having associated time constraints,and/or the like. Events represented as work objects may encompassreal-time communication pathways (which may be duration limited) forenabling real-time audio and/or video discussions between two or moreclient devices 101A-101N, 102. These real-time communication pathwaysmay be established according to one of a plurality of communicationprotocols, which may be exclusive to particular call providers (e.g.,Skype® calls, Zoom® calls, Google Hangouts, WebEx® meetings, and/or thelike). However, it should be understood that various events need notencompass real-time communication pathways. For example, events may bescheduled as single-person appointments (no communication between usersnecessary), as “in-person” meetings at a defined location, astraditional teleconference meetings using traditional telephoneconnectivity, as reminders set by a user, and/or the like.

In addition to data indicative of a communication pathway utilized for aparticular event (if applicable) events comprise additional contextualdata, such as event metadata indicative of an event identifier, an eventoccurrence title, an event location (which may be indicative of thecommunication pathway utilized in certain embodiments), an eventtimestamp, an event runtime identifier, an event date (e.g., an eventstart date and an event end date), an event time (e.g., an event starttime and an event end time), event invitees (e.g., identified byuser-identifying data, such as a unique user identifier, an emailaddress, and/or the like), an event occurrence acceptance identifier, anevent occurrence decline identifier, alert or reminder timing andsettings (e.g., when an alert should be triggered for the event, whattype of alert should be triggered, and/or the like), and/or the like.The event may additionally comprise event content, which may encompassalphanumeric text, event attachments (e.g., other work objects attachedto an event, such as files, emails, messages, and/or the like).Moreover, events may be automatically supplemented during and/or aftercompletion of any corresponding real-time communication component withone or more recordings (e.g., audio recordings, video recordings,transcripts, and/or the like) as may be generated in accordance withvarious call providers.

In various embodiments, events may be generated at client devices101A-101N, 102 and/or at validated external resources 112A-112N (e.g.,third party call provider cloud services) and/or may be disseminatedfrom client devices 101A-101N, 102 and/or validated external resources112A-112N. In certain embodiments, events may be generated via acalendaring application executable locally on a client device 101A-101N,102. The calendaring application may be associated with and/orintegrated with an application of the group-based communication platform105 and/or a validated external resource 112A-112N. Examples ofthird-party calendaring applications that may be utilized in accordancewith various embodiments are iCal®, Microsoft Outlook®, GCal®, and/orthe like. Moreover, events may originate from non-traditional eventgenerators, such as task generators, work flow programs, triagingprograms, and/or the like. These non-traditional event generators maygenerate events and/or reminders for users as output, to be representedwithin separate calendaring applications. The non-traditional eventgenerators may also generate objects specifically usable within thegenerating program, but which includes specific timing data (e.g., a duedate) that may be extracted by the group-based communication platform105 and utilized to construct event data. Context data of events mayvary substantially between event types, the sources of the events,and/or the like.

Particularly when intaking events generated at and/or in associationwith client devices 102 operating with validated external resources, thegroup-based communication platform 105 may be configured to accept eventinvitations as a proxy for particular users having access to thegroup-based communication platform 105 via client devices 101A-101N.Similarly, the group-based communication platform 105 may be configuredto operate as an originator to disseminate events for use by clientdevices 102 (e.g., via validated external resources 112A-112N) to enableinter-platform communication therewith.

Moreover, certain embodiments are configured for backfilling a user'scalendar (e.g., when a new user begins utilizing the group-basedcommunication platform 105), such that events that have been previouslyformed and/or events that have occurred in the past but are not yetknown/reflected at the group-based communication platform 105 may beretrieved by the group-based communication platform 105 (e.g., from theclient device 101A-101N, and/or from a validated external resource112A-112N). Backfilled events may comprise future events (or currentevents) that were not previously provided to the group-basedcommunication platform 105, and/or past events (e.g., those with dateand/or timestamp data occurring prior to the current time and/or thosewith an event completion indicator indicating the event has beencompleted). In certain embodiments, these backfilled events may beretrieved in response to a request provided by the group-basedcommunication platform 105 for backfilled events that is provided to theclient device 101A-101N and/or a validated external resource 105.

A process similar to the backfill process may be utilized to retrieveany events generated while a client device 101A-101N and/or validatedexternal resource 112A-112N is disconnected from the group-basedcommunication platform 105. In such instances, a delta sync process maybe utilized to retrieve any events generated previously but not yetreceived and reflected at the group-based communication platform 105. Inother words, the delta sync process updates and incorporates any changesto data not present during a previous sync.

Event Intake and Dissemination

As discussed above, events may be provided to the group-basedcommunication platform 105 via client devices 101A-101N interactingdirectly with the group-based communication platform 105 and/or from oneor more validated external resources 112A-112N. In certain embodiments,the group-based communication platform 105 may be configured to generateand/or host one or more events (e.g., encompassing audio and/or videocalls). Moreover, the group-based communication platform 105 may beconfigured to disseminate events to identified users, for example, byidentifying intended recipients and for directing events to clientdevices 101A-101N corresponding to the intended recipients.

Events may constitute internal work objects or external work objects,and the group-based communication platform 105 may utilize differentintake procedures for each work object type. FIG. 8 illustrates anexample process for intake processing of internal work object eventsinto the group-based communication platform 105, particularly for callsoriginating at client devices 101A-101N. As shown therein, it should beunderstood that in certain instances—particularly when utilizing avalidated external resource 112A-112N for call (audio or video) hosting,set-up of relevant calls may encompass various data transmissionsbetween client devices 101A-101N, aspects of the group-basedcommunication platform 105, and external computing platforms 112A-112N.

As shown in FIG. 8, the client device 101 initiates a call as shown atBlock 801. Initiating a call may entail generating a calendar objectwithin a native calendaring application on the client device 101 forinitiating a meeting, and/or establishing that the generated meeting isto be conducted via a particular call provider (e.g., Zoom®, WebEx®,and/or the like). The user of the client device 101 may enter suchdetails as a call title, one or more requested participants (and maydesignate such participants as “required,” “optional,” or some otherdesignation). The user may additionally select a call date and time(both start day/time and end day/time).

As shown at Block 802, the client device 101 may communicate with avalidated external resource 112 corresponding to the call provider toestablish details necessary for enabling the call to proceed at thescheduled day time. For example, the validated external resource 112 mayestablish a secure real-time communication protocol to be utilized forthe call, to prevent unauthorized access to the call. Details of thecall, as established at the validated external resource 112, may becommunicated to the client device 101 and are reflected within thecontext data provided to the group-based communication platform 105 fromthe client device 101 and/or may be generated directly within thegroup-based communication platform 105.

Once the user is ready to disseminate the call, the client device 101transmits call details (including details as provided by the user and/ordetails generated and provided by the external computing entity 112) tothe group-based communication platform 105, to be received by theoperation servers 107A-107N. Alternatively, the validated externalresource 112 may directly provide call details to the group-basedcommunication platform 105, and the group-based communication platform105 may match up call details received from the client device 101 andthe validated external resource 112.

The group-based communication platform 105 (e.g., via the operationservers 107A-107N) identifies what type of work object is reflected bythe event. The group-based communication platform 105 need not conductsuch an identification step if the type of work object is already known(e.g., where the internal event work object is generated locally at thegroup-based communication platform 105). The identity of the work objecttype may be utilized to determine an appropriate methodology for parsingthe work object and/or for identifying data to be retrieved from thework object during parsing. Thereafter, the group-based communicationplatform 105 parses context data of the event work object correspondingto the call, as indicated at Block 803, and provides the event to thedatabase storage areas 108A-108N. While parsing the event, the operationservers 107A-107N identifies content of the event (e.g., based on dataprovided by the user at the client device 101), and may identify one ormore other characteristics of the event that may be integrated with themessaging configuration of the group-based communication platform 105.Such identified characteristics may be utilized when disseminating theevent to client devices 101A-101N as a part of the group-basedcommunication platform (e.g., as summary cache objects discussedherein).

When parsing the event, the group-based communication platform 105retrieves the substantive content of the event (if applicable), whichmay be utilized for searching and/or classification of the event.Moreover, the group-based communication platform 105 parses variousportions of the metadata included with the event to identify relevantcharacteristics of the event usable for indexing the event, forclassifying the event, and/or otherwise for providing the event tovarious intended recipients. For example, characteristics unique toevents may inform how to integrate newly received events with anexisting user calendar, including whether any alerts should be providedto one or more users based on existing calendar conflicts with the newlyreceived event.

In certain embodiments, the group-based communication platform 105identifies a sender/generator of an event by parsing the metadatareceived with the event. The sender may be identified by a sending emailaddress, a sending user identifier (particularly applicable for internalwork objects). The group-based communication platform may then determinewhether the sender matches any profiles or other user-identifying datastored at the group-based communication platform 105, if not alreadyidentified based on the user identifier (e.g., stored within databases108A-108N). Determining whether the sender matches existing userprofiles may be utilized to identify a sender's expertise, which may berelevant for establishing appropriate topics for the event.

Moreover, the group-based communication platform 105 identifies intendedrecipients/participants of the event. The intended recipients may beidentified as members of a particular communication channel identifiedas an intended recipient and/or as other recipients (e.g., identified byvalidated external resource identifiers) identified as intendedrecipients of the event. In certain embodiments, the group-basedcommunication platform 105 is configured to cross-reference specificallyenumerated intended recipients (e.g., identified by validated externalresource identifiers) against intended recipients within a particularcommunication channel to identify duplicate recipients. As noted abovein identifying whether a sending user matches any user profiles withinthe group-based communication platform 105, the group-basedcommunication platform 105 determines whether any intended recipientvalidated external resource identifiers match user profiles known to thegroup-based communication platform 105. If a particular intendedrecipient is identified as matching a known user profile, thegroup-based communication platform 105 determines whether the known userprofile is reflected as a member of a communication channel alsoindicated as an intended recipient of the event. If a match isidentified, the group-based communication platform 105 determines therecipient is a duplicate. The group-based communication platform 105 maythen take one or more remedial measures upon identifying a duplicaterecipient, such as refraining from delivering the event to the duplicateuser identifier, if it is determined that the event would show up in auser's calendar based on receipt of the event based on the validatedexternal resource identifier. In other embodiments, the group-basedcommunication platform 105 does not take any remedial actions.

In certain embodiments, the group-based communication platform 105determines how distribution to validated external resources should behandled. In certain embodiments, the group-based communication platform105 parses the event to identify various characteristics of the eventthat may be utilized to retrieve appropriate distribution rules storedwithin the databases 108A-108N for distribution of the particular event.In certain embodiments, the group-based communication platform 105 mayutilize discrete distribution rules for events based on event type, andaccordingly the group-based communication platform 105 is configured toidentify the event type, and utilize the identified event type toretrieve applicable rules for disseminating the event to variousintended recipients. As just one example, events generated to rely oncertain real-time communication protocols (e.g., utilizing calls with aparticular call provider) may be disseminated automatically through thereal-time communication protocol, and accordingly separate distributionprocesses are not needed by the group-based communication platform 105;however, events generated utilizing other real-time communicationprotocols may not have automatic dissemination features through thereal-time communication protocol, and accordingly the group-basedcommunication platform 105 may separately disseminate events to intendedparticipants.

In certain embodiments, due to the time-specific nature of certainevents, the group-based communication platform 105 may establish varioustime-based delivery, reminder, alert, or other configurations forproviding information to users identified as intended recipients of theevents. For example, the group-based communication platform 105 may beconfigured to generate delayed delivery messages for dissemination toone or more of the intended recipients at established times (e.g., aspecified time prior to the start of a scheduled event). Characteristicsof these delayed delivery messages (or other alerts, reminders, and/orthe like) may be generated in accordance with various characteristics ofthe event, such as a defined start time, start date, and/or the like forthe event.

The group-based communication platform 105 may be further configured toadd various events to calendars of intended recipients (at least forthose recipients for which calendars are accessible to the group-basedcommunication platform 105). Such processes may comprise inserting datareflective of the event within calendar data existing for a particularuser. Moreover, the group-based communication platform 105 may beconfigured to compare timing aspects of the event against timing data ofexisting events within a user's calendar to determine whether any timingconflicts exist. In various embodiments, based on identified timingconflicts (e.g., the newly added event at least partially overlaps intime with an existing event on a user's calendar), the group-basedcommunication platform 105 may be configured to generate messages (orother work objects) to the receiving user's client device 101A-101Nand/or the sending user's client device 101A-101N informing the user(s)of the potential timing conflict. In certain embodiments, thegroup-based communication platform 105 may further review calendarsand/or user statuses (which may be determined based at least in part onone or more validated external resources 112A-112N determining whether aparticular user is currently using one or more features of the one ormore validated external resources 112A-112N) of intended recipients toidentify alternative times available (with no conflicts or minimalconflicts) for the event.

The group-based communication platform 105 may further determine whetherthere are any security and/or sharing concerns applicable to the eventwhile parsing the same. The group-based communication platform 105determines what client devices 101A-101N, users, groups, and/or the likemay access the event, which may dictate how the event is utilized and/orindexed (e.g., the security and/or sharing determination may establishwhich work object corpus the event is to be added to).

Moreover, the group-based communication platform may determine whetherany other characteristics exist that are unique to the event. Forexample, particular event-based validated external resources may providespecific metadata content in events that may be utilized by thegroup-based communication platform 105 in establishing supplementalmetadata for the event (as discussed herein). For example, specificformatting data may be utilized for identifying appropriate formattingcorollaries for use with the cache objects.

Moreover, while parsing the event, the operation servers 107A-107N maygenerate a lightweight summary cache object representative of the eventfor rendering within visual containers by client devices 101A-101N thatultimately receive the event as a work-object via the group-basedcommunication platform 105. The summary cache object may be constructedfrom portions of the context data of the event, which may be insertedinto a summary cache object template. Other portions of the template maybe selected and/or populated with data generated by the group-basedcommunication platform 105. The summary cache object may comprise atleast a portion of the content of the event (e.g., the title, time,location/call platform, and/or the like). Examples of such event summarycache objects as may be displayed via a client device 101A-101N areshown at FIGS. 10A-10G. As shown therein, in certain embodiments thesummary cache objects may include an interactive element to interactwith the underlying calendar event in real-time. For example, theinteractive element may be utilized to open lines of communicationassociated with the event, to provide data back to a validated externalresource, and/or the like. For example, the interactive element may beutilized to join the scheduled call. In certain embodiments, theinteractive element for joining the scheduled call may only be availableduring the scheduled time for the call (and/or shortly before and/orshortly after the scheduled call time). Interactive elements foraccepting or ignoring a call may only be available while another user iscalling the user, and interactive elements for ending a call may only beavailable while a call is ongoing. During other time periods, thesummary cache object may only include information about the call.

Moreover, the operation servers 107A-107N may generate an expanded cacheobject having additional detail of the event (e.g., the entirety of theevent content, a listing of participants (together with RSVP details foreach participant), attachments, and/or the like) to be associated withthe event and the summary cache object. In certain embodiments, theexpanded cache object may comprise an interactive portion havingfunctionality similar to that described in relation to the summary cacheobject. In various embodiments, interactive elements for joining a callmay only become available at or shortly before the scheduled start timeof the call.

The summary cache object may then be configured to be interactive forthe receiving client devices 101A-101N, such that clicking/selecting thesummary cache object may cause the client device 101A-101N to requestthe expanded cache object from the group-based communication platform105 for the event. Likewise, the expanded cache object may be similarlyinteractive, and clicking/selecting the expanded cache object may causethe client device 101A-101N to request the full event details from thegroup-based communication platform 105 (e.g., in a format native to thecalendaring application initiating the event).

The databases may generate and append supplemental metadata to the eventafter review of the same, as indicated at Block 804. Such supplementalmetadata may comprise metadata indicative of a topic assigned to theevent. Moreover, such supplemental metadata may be generated inaccordance with one or more artificial intelligence and/ormachine-learning algorithms configured to review the context data, suchas the substantive contents of the event and/or the metadata associatedwith the event to determine an appropriate topic to be assigned to theevent. Certain events from particular validated external resources mayalready include a corollary to topic data (e.g., event labels), whichmay be utilized as a factor in assigning a topic to the event workobject. In certain embodiments, the topics available for assignment maybe established manually by user input, and the database storage areas108A-108N may be configured to select a most-appropriate topic (ormultiple topics) from the established listing. In other embodiments, theartificial intelligence and/or machine learning algorithms may beconfigured for automatically generating a topic in instances in whichpreviously generated topics are deemed too tenuous for description ofthe event.

As a specific example, the database storage areas 108A-108N may utilizecontext data of the event, such as the event content (which may bereviewed utilizing a Tf-idf algorithm in light of a larger dataset ofwork objects to identify relevant topics), event metadata (e.g.,reviewing topics assigned to threads in which the event is disseminated;identifying a sending user and determining the sending user's assignedsubject matter expertise to weigh the potential topics that may beassigned to the event), and/or the like to determine an appropriatetopic.

Ultimately, the database storage areas 108A-108N index the event, asshown at Block 805, which may make the event available for latersearch/retrieval (e.g., for queries satisfying email accessrequirements, such as meeting authorization prerequisites to view themessage).

In certain embodiments, the operation servers 107A-107N may disseminatethe event (e.g., as a summary cache object) to intended recipients, asindicated at Block 806. In various embodiments, the group-basedcommunication platform may disseminate the summary cache object toclient devices 101A-101N. Those client devices 101A-101N may receive thedetails of the event (e.g., the lightweight cache work object), asindicated at Block 807, and may render the event details (e.g., thesummary cache object) for display, as indicated at Block 808. Renderingthe event (e.g., the lightweight cache work object may compriserendering the event to appear as a native work object of the group-basedcommunication platform 105). Such renders may appear as objectsdisseminated to the user, which may provide certain data regarding thework object for the user of the client device 101A-101N.

Moreover, the operation servers 107A-107N disseminate the event (e.g.,as a summary cache object, as the full event, and/or the like) tointended recipients accessing the communication exchange via validatedexternal resources 112A-112N as shown at Blocks 809-811. As discussedherein, the group-based communication platform may identify specificrules for disseminating events to various validated external resources,and accordingly dissemination may be performed in accordance with rulesretrieved while parsing the event.

Recipients reachable via one or more validated external resources112A-112N may receive events disseminated from the group-basedcommunication platform 105 by receipt at the applicable validatedexternal resource 112A-112N (as indicated at Block 809), which may thendisseminate the events to client devices 102 (e.g., with an appropriatestyle guide applicable to work objects common to the validated externalresource 112A-112N). The client device 102 may then receive the eventand render the event for display, as indicated at Blocks 810-811.

Because the validated external resources 112A-112N may utilize separatestyle guides for work object display, the group-based communicationplatform 105 may be configured to transmit the events to the validatedexternal resources 112A-112N via one or more formatting agnostic datatransmission protocols. For example, the group-based communicationplatform 105 may pass event data to validated external resources112A-112N via one or more APIs, via one or more proxy endpointsproviding event data in a format discernable to the validated externalresource 112A-112N to automatically identify various components of theevent data (e.g., XML formatting providing various labeled containers ofdata), and/or the like. The validated external resource 112A-112N maythen apply self-imposed formatting guides to the events and/or mayautomatically omit various portions of the event data, as needed tocomply with the self-imposed formatting.

As shown at Blocks 812-813, client devices 101A-101N, 102 participate inthe call, hosted by the validated external resource 112 (oralternatively hosted by the group-based communication platform 105), asindicated at Block 814. As noted, the call may be a video call, an audiocall, and/or the like, and may constitute real-time communicationbetween participants of the call. The call may be hosted through a modalaccessible within the group-based communication interface accessible viaclient devices 101A-101N, and/or the call may be accessible via otherapplications accessible via client devices 101A-101N, 102.

During and/or after the call, the validated external resource 112 maygenerate a recording of the call (e.g., a video recording, an audiorecording, a transcript of the call, and/or the like), as indicated atBlock 815. Although not shown, the recording may be disseminated toparticipants of the call (e.g., by transmitting the recording to clientdevices 101A-101N, 102 of participants of the call) based ondissemination rules. The recording may be passed to the group-basedcommunication platform 105, which may parse the call recording, asindicated at Block 816. Recordings are treated as other call contextdata in accordance with certain embodiments, and may be parsed asdiscussed herein to identify aspects of the call usable for indexing theevent. As shown at Blocks 817-818, the recording may be passed to thedatabase storage areas 108A-108N, which may add and/or modify thesupplemental metadata associated with the call (e.g., to reflectadditional topics, to remove previous topics selected based on metadataassociated with the call, and/or the like). The supplemental metadataassociated with the call may thus be updated to reflect discussionsactually occurring during the call.

FIG. 9 illustrates an example process for intake processing of eventsinto the group-based communication platform 105 for calls originating ata client device 102, which is in communication with the group-basedcommunication platform 105 through a validated external resource 112, asdiscussed herein.

As shown in FIG. 9, the client device 102 initiates a call as shown atBlock 901. Initiating a call may entail generating a calendar objectwithin a native calendaring application on the client device 102 forinitiating a meeting, and/or establishing that the generated meeting isto be conducted via a particular call provider (e.g., Zoom®, WebEx®,and/or the like). Such calls are considered external work objects. Theuser of the client device 102 may enter such details as a call title,one or more requested participants (and may designate such participantsas “required,” “optional,” or some other designation). The user mayadditionally select a call date and time (both start day/time and endday/time).

As shown at Block 902, the client device 102 may communicate with avalidated external resource 112 corresponding to the call provider toestablish details necessary for enabling the call to proceed at thescheduled day time. For example, the validated external resource 112 mayestablish a secure real-time communication protocol to be utilized forthe call, to prevent unauthorized access to the call. Details of thecall, as established at the validated external resource 112, may becommunicated to the client device 102 and/or the group-basedcommunication platform 105.

Once the user is ready to disseminate the call, the client device 101(and/or the validated external resource 105) transmits call details(including details as provided by the user and/or details generated andprovided by the external computing entity 112) to the group-basedcommunication platform 105, to be received by the operation servers107A-107N. The validated external resource may disseminate the call datadirectly to all intended recipients, or the validated external resourcemay rely on the group-based communication platform 105 to disseminatethe call to at least a portion of the intended recipients. For example,if a channel is indicated as an intended recipient of the event (e.g.,based on a channel email utilized to provide the event to thegroup-based communication platform 105, or based on anothercommunication pathway utilized to provide the event to the group-basedcommunication platform 105), the call details are disseminated to one ormore members of the identified channel by the group-based communicationplatform 105.

The group-based communication platform 105 (e.g., via the operationservers 107A-107N) parses the context data of the event work objectcorresponding to the call, as indicated at Block 903, and provides theevent to the database storage areas 108A-108N. While parsing the event,the operation servers 107A-107N identifies content of the event (e.g.,based on data provided by the user at the client device 101), and mayidentify one or more other characteristics of the event that may beintegrated with the messaging configuration of the group-basedcommunication platform 105. Such identified characteristics may beutilized when disseminating the event to client devices 101A-101N as apart of the group-based communication platform (e.g., as summary cacheobjects discussed herein).

When parsing the event, the group-based communication platform retrievesthe substantive content of the event (if applicable), which may beutilized for searching and/or classification of the event. Moreover, thegroup-based communication platform 105 parses various portions of themetadata included with the event to identify relevant characteristics ofthe event usable for indexing the event, for classifying the event,and/or otherwise for providing the event to various intended recipients.For example, characteristics unique to events may inform how tointegrate newly received events with an existing user calendar,including whether any alerts should be provided to one or more usersbased on existing calendar conflicts with the newly received event.

In certain embodiments, the group-based communication platform 105identifies a sender/generator of an event by parsing the metadatareceived with the event. The sender may be identified by a sending emailaddress, a sending user identifier (particularly applicable for internalwork objects), and/or a validated external resource identifier. Thegroup-based communication platform may then determine whether the sendermatches any profiles or other user-identifying data stored at thegroup-based communication platform 105, if not already identified basedon the user identifier (e.g., stored within databases 108A-108N).Determining whether the sender matches existing user profiles may beutilized to identify a sender's expertise, which may be relevant forestablishing appropriate topics for the event.

Moreover, the group-based communication platform 105 identifies intendedrecipients/participants of the event. The intended recipients may beidentified as members of a particular communication channel identifiedas an intended recipient and/or as other recipients (e.g., identified byvalidated external resource identifiers) identified as intendedrecipients of the event. In certain embodiments, the group-basedcommunication platform 105 is configured to cross-reference specificallyenumerated intended recipients (e.g., identified by validated externalresource identifiers) against intended recipients within a particularcommunication channel to identify duplicate recipients. As noted abovein identifying whether a sending user matches any user profiles withinthe group-based communication platform 105, the group-basedcommunication platform 105 determines whether any intended recipientvalidated external resource identifiers match user profiles known to thegroup-based communication platform 105. If a particular intendedrecipient is identified as matching a known user profile, thegroup-based communication platform 105 determines whether the known userprofile is reflected as a member of a communication channel alsoindicated as an intended recipient of the event. If a match isidentified, the group-based communication platform 105 determines therecipient is a duplicate. The group-based communication platform 105 maythen take one or more remedial measures upon identifying a duplicaterecipient, such as refraining from delivering the event to the duplicateuser identifier, if it is determined that the event would show up in auser's calendar based on receipt of the event based on the validatedexternal resource identifier. In other embodiments, the group-basedcommunication platform 105 does not take any remedial actions.

In certain embodiments, the group-based communication platform 105determines how distribution to validated external resources should behandled. In certain embodiments, the group-based communication platform105 parses the event to identify various characteristics of the eventthat may be utilized to retrieve appropriate distribution rules storedwithin the databases 108A-108N for distribution of the particular event.In certain embodiments, the group-based communication platform 105 mayutilize discrete distribution rules for events based on event type, andaccordingly the group-based communication platform 105 is configured toidentify the event type, and utilize the identified event type toretrieve applicable rules for disseminating the event to variousintended recipients. As just one example, events generated to rely oncertain real-time communication protocols (e.g., utilizing calls with aparticular call provider) may be disseminated automatically through thereal-time communication protocol, and accordingly separate distributionprocesses are not needed by the group-based communication platform 105;however, events generated utilizing other real-time communicationprotocols may not have automatic dissemination features through thereal-time communication protocol, and accordingly the group-basedcommunication platform 105 may separately disseminate events to intendedparticipants.

In certain embodiments, due to the time-specific nature of certainevents, the group-based communication platform 105 may establish varioustime-based delivery, reminder, alert, or other configurations forproviding information to users identified as intended recipients of theevents. For example, the group-based communication platform 105 may beconfigured to generate delayed delivery messages for dissemination toone or more of the intended recipients at established times (e.g., aspecified time prior to the start of a scheduled event). Characteristicsof these delayed delivery messages (or other alerts, reminders, and/orthe like) may be generated in accordance with various characteristics ofthe event, such as a defined start time, start date, and/or the like forthe event.

The group-based communication platform 105 may be further configured toadd various events to calendars of intended recipients (at least forthose recipients for which calendars are accessible to the group-basedcommunication platform 105). Such processes may comprise inserting datareflective of the event within calendar data existing for a particularuser. Moreover, the group-based communication platform 105 may beconfigured to compare timing aspects of the event against timing data ofexisting events within a user's calendar to determine whether any timingconflicts exist. In various embodiments, based on identified timingconflicts (e.g., the newly added event at least partially overlaps intime with an existing event on a user's calendar), the group-basedcommunication platform 105 may be configured to generate messages (orother work objects) to the receiving user's client device 101A-101Nand/or the sending user's client device 101A-101N informing the user(s)of the potential timing conflict. In certain embodiments, thegroup-based communication platform 105 may further review calendars ofintended recipients to identify alternative times available (with noconflicts or minimal conflicts) for the event.

The group-based communication platform 105 may further determine whetherthere are any security and/or sharing concerns applicable to the eventwhile parsing the same. The group-based communication platform 105determines what client devices 101A-101N, users, groups, and/or the likemay access the event, which may dictate how the event is utilized and/orindexed (e.g., the security and/or sharing determination may establishwhich work object corpus the event is to be added to).

Moreover, the group-based communication platform may determine whetherany other characteristics exist that are unique to the event. Forexample, particular event-based validated external resources may providespecific metadata content in events that may be utilized by thegroup-based communication platform 105 in establishing supplementalmetadata for the event (as discussed herein). For example, specificformatting data may be utilized for identifying appropriate formattingcorollaries for use with the cache objects.

Moreover, while parsing the event, the operation servers 107A-107N maygenerate a lightweight summary cache object representative of the eventfor rendering within visual containers by client devices 101A-101N thatultimately receive the event as a work-object via the group-basedcommunication platform 105. The summary cache object may be constructedfrom portions of the context data of the event, which may be insertedinto a summary cache object template. Other portions of the template maybe selected and/or populated with data generated by the group-basedcommunication platform 105. The summary cache object may comprise atleast a portion of the content of the event (e.g., the title, time,location/call platform, and/or the like). In certain embodiments, thesummary cache object may be configured to remind a user to join thescheduled event (e.g., via the validated external resource), as apassive reminder, or the summary cache object may be an active reminderconfigured to facilitate the user joining the scheduled event, forexample, with interactive portions to enable the user to directly jointhe event. In certain embodiments the summary cache objects may includean interactive element to interact with the underlying calendar event inreal-time. For example, the interactive element may be utilized to openlines of communication associated with the event, to provide data backto a validated external resource, and/or the like. For example, theinteractive element may be utilized to join the scheduled call. Incertain embodiments, the interactive element for joining the scheduledcall may only be available during the scheduled time for the call(and/or shortly before and/or shortly after the scheduled call time).Interactive elements for accepting or ignoring a call may only beavailable while another user is calling the user, and interactiveelements for ending a call may only be available while a call isongoing. During other time periods, the summary cache object may onlyinclude information about the call.

Moreover, the operation servers 107A-107N may generate an expanded cacheobject having additional detail of the event (e.g., the entirety of theevent content, a listing of participants (together with RSVP details foreach participant), attachments, and/or the like) to be associated withthe event and the summary cache object. In certain embodiments, theexpanded cache object may comprise an interactive portion withfunctionality similar to that described in relation to the summaryobject. In various embodiments, interactive elements for joining a callmay only become available at or shortly before the scheduled start timeof the call.

The summary cache object may then be configured to be interactive forthe receiving client devices 101A-101N, such that clicking/selecting thesummary cache object may cause the client device 101A-101N to requestthe expanded cache object from the group-based communication platform105 for the event. Likewise, the expanded cache object may be similarlyinteractive, and clicking/selecting the expanded cache object may causethe client device 101A-101N to request the full event details from thegroup-based communication platform 105 (e.g., in a format native to thecalendaring application initiating the event).

The databases may generate and append supplemental metadata to the eventafter review of the same, as indicated at Block 904. Such supplementalmetadata may comprise metadata indicative of a topic assigned to theevent. Moreover, such supplemental metadata may be generated inaccordance with one or more artificial intelligence and/ormachine-learning algorithms configured to review the context data, suchas substantive contents of the event and/or the metadata associated withthe event to determine an appropriate topic to be assigned to the event.Certain events from particular validated external resources may alreadyinclude a corollary to topic data (e.g., event labels), which may beutilized as a factor in assigning a topic to the event work object. Incertain embodiments, the topics available for assignment may beestablished manually by user input, and the database storage areas108A-108N may be configured to select a most-appropriate topic (ormultiple topics) from the established listing. In other embodiments, theartificial intelligence and/or machine learning algorithms may beconfigured for automatically generating a topic in instances in whichpreviously generated topics are deemed too tenuous for description ofthe event.

As a specific example, the database storage areas 108A-108N may utilizecontext of the event, such as the event content (which may be reviewedutilizing a Tf-idf algorithm in light of a larger dataset of workobjects to identify relevant topics), event metadata (e.g., reviewingtopics assigned to threads in which the event is disseminated;identifying a sending user and determining the sending user's assignedsubject matter expertise to weigh the potential topics that may beassigned to the event), and/or the like to determine an appropriatetopic.

Ultimately, the database storage areas 108A-108N indexes the event, asshown at Block 905, which may make the event available for latersearch/retrieval (e.g., for queries satisfying email accessrequirements, such as meeting authorization prerequisites to view themessage).

In certain embodiments, the operation servers 107A-107N may disseminatethe event (e.g., as a summary cache object) to intended recipients, asindicated at Block 906. In various embodiments, the group-basedcommunication platform may disseminate the summary cache object toclient devices 101A-101N. Those client devices 101A-101N may receive thedetails of the event (e.g., the lightweight summary cache work object),as indicated at Block 907, and may render the event details (e.g., thesummary cache object) for display, as indicated at Block 908. Renderingthe event (e.g., the lightweight summary cache work object) may compriserendering the event to appear as a native work object of the group-basedcommunication platform 105. Such renders may appear as objectsdisseminated to the user, which may provide certain data regarding thework object for the user of the client device 101A-101N.

Moreover, the operation servers 107A-107N disseminate the event (e.g.,as a summary cache object, as the full event, and/or the like) tointended recipients accessing the communication exchange via validatedexternal resources 112A-112N as shown at Blocks 909-911. As discussedherein, the group-based communication platform may identify specificrules for disseminating events to various validated external resources,and accordingly dissemination may be performed in accordance with rulesretrieved while parsing the event.

Recipients reachable via one or more validated external resources112A-112N may receive events disseminated from the group-basedcommunication platform 105 by receipt at the applicable validatedexternal resource 112A-112N (as indicated at Block 909), which may thendisseminate the events to client devices 102 (e.g., with an appropriatestyle guide applicable to work objects common to the validated externalresource 112A-112N). The client device 102 may then receive the eventand render the event for display, as indicated at Blocks 910-911.However, because the event is generated at the validated externalresource 112A-112N, the client device 102 may receive the event directlyfrom the generating validated external resource 112A-112N.

Because the validated external resources 112A-112N may utilize separatestyle guides for work object display, the group-based communicationplatform 105 may be configured to transmit the events to the validatedexternal resources 112A-112N via one or more formatting agnostic datatransmission protocols. For example, the group-based communicationplatform 105 may pass event data to validated external resources112A-112N via one or more APIs, via one or more proxy endpointsproviding event data in a format discernable to the validated externalresource 112A-112N to automatically identify various components of theevent data (e.g., XML formatting providing various labeled containers ofdata), and/or the like. The validated external resource 112A-112N maythen apply self-imposed formatting guides to the events and/or mayautomatically omit various portions of the event data, as needed tocomply with the self-imposed formatting.

As shown at Blocks 912-913, client devices 101A-101N, 102 participate inthe call, hosted by the validated external resource 112 (oralternatively hosted by the group-based communication platform 105), asindicated at Block 914. As noted, the call may be a video call, an audiocall, and/or the like, and may constitute real-time communicationbetween participants of the call. The call may be accessible via a modal(or other container) displayable within the group-based communicationinterface, as discussed herein.

During and/or after the call, the validated external resource 112 maygenerate a recording of the call (e.g., a video recording, an audiorecording, a transcript of the call, and/or the like), as indicated atBlock 915. Although not shown, the recording may be disseminated toparticipants of the call (e.g., by transmitting the recording to clientdevices 101A-101N, 102 of participants of the call) based on determineddissemination rules. The recording may be passed to the group-basedcommunication platform 105, which may parse the call recording, asindicated at Block 916. The call recording may be treated as additionalcontext data, subject to parsing as discussed above. As shown at Blocks917-918, the recording may be passed to the database storage areas108A-108N, which may add and/or modify the supplemental metadataassociated with the call (e.g., to reflect additional topics, to removeprevious topics selected based on metadata associated with the call,and/or the like). The supplemental metadata associated with the call maythus be updated to reflect discussions actually occurring during thecall.

Moreover, although not explicitly illustrated in FIGS. 7-8, it should beunderstood that calls (including video calls and/or audio calls) neednot be scheduled prior to participation in the call. In suchembodiments, a first user (e.g., a user of a client device 101) may calla second user (e.g., a user of a client device 102) via a particularvalidated external resource 112A. In instances in which the validatedexternal resource has real-time communication established with thegroup-based communication platform 105, cache objects relating to thecalls may be shared in real-time and provided to one or more clientdevices 101A-101N, 102 to indicate that a call is requested (e.g., “UserX is calling you”), that a call is in progress (e.g., “Call in Progresswith User X, User Y, and three more”), and/or that a call has ended.Information regarding the call may be passed between the one or moreclient devices 101A-101N, 102, the group-based communication platform105 and/or one or more validated external resources 112A-112N, asapplicable. Information regarding the call may be provided to userswithin visual containers providing summary data regarding the call, andwhich may include one or more interactive elements to initiate a call,to ignore an incoming call, to answer an incoming call, to end a currentcall, and/or the like.

It should be understood that in embodiments in which a call is notpre-scheduled, the group based communication platform 105 may bespecifically configured to parse call recordings (e.g., transcripts,audio recordings, video recordings, and/or the like) together with othercontext data to make a first determination of relevant supplementarymetadata to be appended to the call data. For example, the context datamay be parsed to determine how the call is made (e.g., via whatvalidated external resource is used for the call, if any), when the callwas made (e.g., start time and date, and end time and date), whethermetadata associated with the call indicates that the call wasunscheduled, who was invited to the call (e.g., who was the call placedto), who placed the call, and/or the like. While parsing the unscheduledcall, the group-based communication platform 105 may identify asender/generator of an event by parsing the metadata received with theevent. The sender may be identified by a sending email address, asending user identifier (particularly applicable for internal workobjects), and/or a validated external resource identifier. Thegroup-based communication platform may then determine whether the sendermatches any profiles or other user-identifying data stored at thegroup-based communication platform 105, if not already identified basedon the user identifier (e.g., stored within databases 108A-108N).Determining whether the sender matches existing user profiles may beutilized to identify a sender's expertise, which may be relevant forestablishing appropriate topics for the event.

Moreover, the group-based communication platform 105 may add the eventto one or more calendars associated with participants of the call (e.g.,the sending/generating user and/or the receiving users), as historicalevents that may be searched by those users. Such processes may compriseinserting data reflective of the event within calendar data existing fora particular user.

The group-based communication platform 105 may further determine whetherthere are any security and/or sharing concerns applicable to the eventwhile parsing the same. The group-based communication platform 105determines what client devices 101A-101N, users, groups, and/or the likemay access the event, which may dictate how the event is utilized and/orindexed (e.g., the security and/or sharing determination may establishwhich work object corpus the event is to be added to).

Moreover, the group-based communication platform may determine whetherany other characteristics exist that are unique to the event. Forexample, particular event-based validated external resources may providespecific metadata content in events that may be utilized by thegroup-based communication platform 105 in establishing supplementalmetadata for the event (as discussed herein). For example, specificformatting data may be utilized for identifying appropriate formattingcorollaries for use with the cache objects. The call may then be indexedbased at least in part on the determined supplementary data, asdiscussed herein.

FIG. 11 illustrates an example process for intaking processing ofappointment related events (e.g., those events not encompassing a callperformed through the group-based communication platform 105 or avalidated external resource 112). These appointment events may beinternal work objects or external work objects. These appointment eventsmay constitute teleconferences (taking place over phone lines, forexample, without integration with a cloud-based call service), in-personmeetings, and/or individual appointments (private appointments of aparticular individual). In accordance with certain embodiments, appointrelated events are generated at one or more external (or internal)calendar applications, such as iCal, Google Calendar, Microsoft Outlookcalendar, and/or the like. Such calendar applications include variousfeatures for enabling users to enter information regarding a scheduledcalendar event, such as the title of the event, time and date of theevent (both beginning and ending), location of the event, invitedparticipants of the event, the event creator, and/or the like.

As shown in FIG. 11, a client device 101 initiates an appointment asshown at Block 1101 (it should be understood that similar processes maybe performed via client device 102). Initiating an appointment mayentail generating a calendar object within a native calendaringapplication on the client device 101 for initiating a meeting, and/orother appointment, generating an object having particular timingconstraints (e.g., a workflow object, a task object, and/or the like).The user of the client device 101 may enter such details as anappointment title, one or more requested participants (and may designatesuch participants as “required,” “optional,” or some other designation).The user may additionally select an appointment date and time (bothstart day/time and end day/time).

Once the user is ready to disseminate the appointment (or to save theappointment with the group-based communication platform 105, even if noother participants are to be invited to the appointment), the clientdevice 101 transmits appointment details to the group-basedcommunication platform 105, to be received by the operation servers107A-107N. Alternatively, a validated external resource 112 may provideappointment details to the group-based communication platform 105 if theevent was generated at client device 102. Details of the event may bereflected within context data provided to the group-based communicationplatform 105 or may be generated at the group-based communicationplatform 105. For non-calendar objects with timing constraints (e.g.,work flow objects specifically usable within a defined validatedexternal resource), context data provided may be utilized to generate acalendar work object within the group-based communication platform 105.

The group-based communication platform 105 (e.g., via the operationservers 107A-107N) identifies what type of work object is reflected bythe event. The group-based communication platform 105 need not conductsuch an identification step if the type of work object is already known(e.g., where the internal event work object is generated locally at thegroup-based communication platform 105). The identity of the work objecttype may be utilized to determine an appropriate methodology for parsingthe work object and/or for identifying data to be retrieved from thework object during parsing. Thereafter, the group-based communicationplatform 105 parses context data of the event work object correspondingto the appointment, as indicated at Block 1102, and provides the eventto the database storage areas 108A-108N. While parsing the event, theoperation servers 107A-107N identifies content of the event (e.g., basedon data provided by the user at the client device 101), and may identifyone or more other characteristics of the event that may be integratedwith the messaging configuration of the group-based communicationplatform 105. Such identified characteristics may be utilized whendisseminating the event to client devices 101A-101N as a part of thegroup-based communication platform (e.g., as summary cache objectsdiscussed herein).

When parsing the event, the group-based communication platform 105retrieves the substantive content of the event (if applicable), whichmay be utilized for searching and/or classification of the event.Moreover, the group-based communication platform 105 parses variousportions of the metadata included with the event to identify relevantcharacteristics of the event usable for indexing the event, forclassifying the event, and/or otherwise for providing the event tovarious intended recipients. For example, characteristics unique toevents may inform how to integrate newly received events with anexisting user calendar, including whether any alerts should be providedto one or more users based on existing calendar conflicts with the newlyreceived event.

In certain embodiments, the group-based communication platform 105identifies a sender/generator of an event by parsing the metadatareceived with the event. The sender may be identified by a sending emailaddress, a sending user identifier (particularly applicable for internalwork objects). The group-based communication platform may then determinewhether the sender matches any profiles or other user-identifying datastored at the group-based communication platform 105, if not alreadyidentified based on the user identifier (e.g., stored within databases108A-108N). Determining whether the sender matches existing userprofiles may be utilized to identify a sender's expertise, which may berelevant for establishing appropriate topics for the event.

If applicable, the group-based communication platform 105 identifiesintended recipients/participants of the event. However, it should beunderstood that in certain embodiments, the appointment event objectneed not have any intended recipients, as the generating user identifiermay be the only participant in the event (e.g., a private event). Theintended recipients may be identified as members of a particularcommunication channel identified as an intended recipient and/or asother recipients (e.g., identified by validated external resourceidentifiers) identified as intended recipients of the event. In certainembodiments, the group-based communication platform 105 is configured tocross-reference specifically enumerated intended recipients (e.g.,identified by validated external resource identifiers) against intendedrecipients within a particular communication channel to identifyduplicate recipients. As noted above in identifying whether a sendinguser matches any user profiles within the group-based communicationplatform 105, the group-based communication platform 105 determineswhether any intended recipient validated external resource identifiersmatch user profiles known to the group-based communication platform 105.If a particular intended recipient is identified as matching a knownuser profile, the group-based communication platform 105 determineswhether the known user profile is reflected as a member of acommunication channel also indicated as an intended recipient of theevent. If a match is identified, the group-based communication platform105 determines the recipient is a duplicate. The group-basedcommunication platform 105 may then take one or more remedial measuresupon identifying a duplicate recipient, such as refraining fromdelivering the event to the duplicate user identifier, if it isdetermined that the event would show up in a user's calendar based onreceipt of the event based on the validated external resourceidentifier. In other embodiments, the group-based communication platform105 does not take any remedial actions.

In certain embodiments, due to the time-specific nature of certainevents, the group-based communication platform 105 may establish varioustime-based delivery, reminder, alert, or other configurations forproviding information to users identified as intended recipients of theevents. For example, the group-based communication platform 105 may beconfigured to generate delayed delivery messages for dissemination toone or more of the intended recipients at established times (e.g., aspecified time prior to the start of a scheduled event). Characteristicsof these delayed delivery messages (or other alerts, reminders, and/orthe like) may be generated in accordance with various characteristics ofthe event, such as a defined start time, start date, and/or the like forthe event.

The group-based communication platform 105 may be further configured toadd various events to calendars of intended recipients (at least forthose recipients for which calendars are accessible to the group-basedcommunication platform 105). Such processes may comprise inserting datareflective of the event within calendar data existing for a particularuser. Moreover, the group-based communication platform 105 may beconfigured to compare timing aspects of the event against timing data ofexisting events within a user's calendar to determine whether any timingconflicts exist. In various embodiments, based on identified timingconflicts (e.g., the newly added event at least partially overlaps intime with an existing event on a user's calendar), the group-basedcommunication platform 105 may be configured to generate messages (orother work objects) to the receiving user's client device 101A-101Nand/or the sending user's client device 101A-101N informing the user(s)of the potential timing conflict. In certain embodiments, thegroup-based communication platform 105 may further review calendars ofintended recipients to identify alternative times available (with noconflicts or minimal conflicts) for the event.

The group-based communication platform 105 may further determine whetherthere are any security and/or sharing concerns applicable to the eventwhile parsing the same. The group-based communication platform 105determines what client devices 101A-101N, users, groups, and/or the likemay access the event, which may dictate how the event is utilized and/orindexed (e.g., the security and/or sharing determination may establishwhich work object corpus the event is to be added to).

Moreover, the group-based communication platform may determine whetherany other characteristics exist that are unique to the event. Forexample, particular event-based validated external resources may providespecific metadata content in events that may be utilized by thegroup-based communication platform 105 in establishing supplementalmetadata for the event (as discussed herein). For example, specificformatting data may be utilized for identifying appropriate formattingcorollaries for use with the cache objects.

Moreover, while parsing the event, the operation servers 107A-107N maygenerate a lightweight summary cache object representative of the eventfor rendering within visual containers by client devices 101A-101N thatultimately receive the event as a work-object via the group-basedcommunication platform 105. The summary cache object may be constructedfrom portions of the context data of the event, which may be insertedinto a summary cache object template. Other portions of the template maybe selected and/or populated with data generated by the group-basedcommunication platform 105. The summary cache object may comprise atleast a portion of the content of the event (e.g., the title, time,location, and/or the like).

Moreover, the operation servers 107A-107N may generate an expanded cacheobject having additional detail of the event (e.g., the entirety of theevent content, a listing of participants (together with RSVP details foreach participant, if applicable), attachments, and/or the like) to beassociated with the event and the summary cache object.

The summary cache object may then be configured to be interactive forthe receiving client devices 101A-101N, such that clicking/selecting thesummary cache object may cause the client device 101A-101N to requestthe expanded cache object from the group-based communication platform105 for the event. Likewise, the expanded cache object may be similarlyinteractive, and clicking/selecting the expanded cache object may causethe client device 101A-101N to request the full event details from thegroup-based communication platform 105 (e.g., in a format native to thecalendaring application initiating the event).

The databases may generate and append supplemental metadata to the eventafter review of the same, as indicated at Block 1103. Such supplementalmetadata may comprise metadata indicative of a topic assigned to theevent. Moreover, such supplemental metadata may be generated inaccordance with one or more artificial intelligence and/ormachine-learning algorithms configured to review the context data, suchas substantive contents of the event and/or the metadata associated withthe event to determine an appropriate topic to be assigned to the event.Certain events from particular validated external resources may alreadyinclude a corollary to topic data (e.g., event labels), which may beutilized as a factor in assigning a topic to the event work object. Incertain embodiments, the topics available for assignment may beestablished manually by user input, and the database storage areas108A-108N may be configured to select a most-appropriate topic (ormultiple topics) from the established listing. In other embodiments, theartificial intelligence and/or machine learning algorithms may beconfigured for automatically generating a topic in instances in whichpreviously generated topics are deemed too tenuous for description ofthe event.

As a specific example, the database storage areas 108A-108N may utilizecontext data of the event, such as the event content (which may bereviewed utilizing a Tf-idf algorithm in light of a larger dataset ofwork objects to identify relevant topics), event metadata (e.g.,reviewing topics assigned to threads in which the event is disseminated;identifying a sending user and determining the sending user's assignedsubject matter expertise to weigh the potential topics that may beassigned to the event), and/or the like to determine an appropriatetopic.

Ultimately, the database storage areas 108A-108N index the event, asshown at Block 1104, which may make the event available for latersearch/retrieval (e.g., for queries satisfying email accessrequirements, such as meeting authorization prerequisites to view themessage).

In instances in which the event is a private appointment or is otherwiseonly applicable to the creating user, the process may end here. Incertain embodiments, the operation servers 107A-107N may provide eventdetails back to the originating client device 101 (e.g., as a summarycache object; as an expanded cache object; and/or the like) for displayon the originating client device 101 only. However, in otherembodiments, no further activity may occur.

However, for meetings and other multi-person appointments, the operationservers 107A-107N may disseminate the event (e.g., as a summary cacheobject) to intended recipients, as indicated at Block 1105. As discussedherein, the group-based communication platform may identify specificrules for disseminating events to various validated external resources,and accordingly dissemination may be performed in accordance with rulesretrieved while parsing the event. In various embodiments, thegroup-based communication platform may disseminate the summary cacheobject to client devices 101A-101N. Those client devices 101A-101N mayreceive the details of the event (e.g., the lightweight cache workobject), as indicated at Block 1106, and may render the event details(e.g., the summary cache object) for display, as indicated at Block1107. Rendering the event (e.g., the lightweight cache work object maycomprise rendering the event to appear as a native work object of thegroup-based communication platform 105). Such renders may appear asobjects disseminated to the user, which may provide certain dataregarding the work object for the user of the client device 101A-101N.

As shown in FIG. 12, a summary cache object displayable for a particularappointment-style event may be configured for display with one or moreinteractive portions. As shown therein, an appointment summary cacheobject may comprise one or more optional interactive portions configuredto receive user input indicative of whether a user intends on attendingthe event. As shown in FIG. 12, the summary cache object to be displayedto a user may comprise an “are you attending?” or a “going?” portion,accompanied with three buttons, “yes,” “no,” and “maybe.” When a userselects one of the buttons associated with the summary cache object,data is transmitted back to the group-based communication platform 105,and the work object and associated metadata is updated to reflect thereceived attendance data from the user. For example, the total number ofinvitees who have selected a particular attendance status may beupdated, and metadata associated with the particular user (stored inassociation with the event) may be updated to indicate that theparticular user has selected an attendance option. For example, themetadata associated with the event work object may be updated to reflectthe total number of invitees who have indicated they plan to attend, thetotal number of attendees who have indicated that they do not plan toattend, the total number of attendees who have indicated they mayattend, and the total number of attendees who have not provided anattendance response. Moreover, metadata associated with each invitee maybe updated to reflect how the invitee has responded to the event workobject.

Moreover, the operation servers 107A-107N disseminate the event (e.g.,as a summary cache object, as the full event, and/or the like) tointended recipients accessing the communication exchange via validatedexternal resources 112A-112N as shown at Blocks 1108-1110.

Recipients reachable via one or more validated external resources112A-112N may receive events disseminated from the group-basedcommunication platform 105 by receipt at the applicable validatedexternal resource 112A-112N (as indicated at Block 1108), which may thendisseminate the events to client devices 102 (e.g., with an appropriatestyle guide applicable to work objects common to the validated externalresource 112A-112N). The client device 102 may then receive the eventand render the event for display, as indicated at Blocks 1109-1110.

Because the validated external resources 112A-112N may utilize separatestyle guides for work object display, the group-based communicationplatform 105 may be configured to transmit the events to the validatedexternal resources 112A-112N via one or more formatting agnostic datatransmission protocols. For example, the group-based communicationplatform 105 may pass event data to validated external resources112A-112N via one or more APIs, via one or more proxy endpointsproviding event data in a format discernable to the validated externalresource 112A-112N to automatically identify various components of theevent data (e.g., XML formatting providing various labeled containers ofdata), and/or the like. The validated external resource 112A-112N maythen apply self-imposed formatting guides to the events and/or mayautomatically omit various portions of the event data, as needed tocomply with the self-imposed formatting.

In certain embodiments, context data of events may contain dataindicative of the status of the underlying event (e.g., a reminder maybe cleared upon completion of the underlying task/event). Accordingly,the group-based communication platform 105 may be configured toperiodically update the status of various events, and may mark variousevents as complete, if applicable. By marking an event as complete, theunderlying context data of the event may be updated within variouscalendars of the intended recipients/participants of the event.

Files

Files are a type of external work object for which other type-specificprocesses are not employed for distribution of those work objects.Typically, files are distributed together with another work object(e.g., as an attachment to a message, as an attachment to an email, asan attachment to an event, and/or the like), however it should beunderstood that files may be disseminated alone in certain instances.Files may be executable by any of a variety of applications operating ona client device 101A-101N, 102, as may be determined based at least inpart on a file extension provided with each file. For example, fileshaving an extension of “.doc” or “.docx” may be executable by wordprocessing applications (e.g., Microsoft Word® or Google Docs); fileshaving an extension of “.html” or “.php” may be executable by browsersof a client device; and/or the like. Other file extensions, such as thenon-limiting examples of “.stp”, “.zip”, “.rar”, “.exe”, and/or the likemay similarly be exchanged in accordance with various embodiments.

Files may comprise content data accessible via specially configuredprograms (also referred to herein as “apps” or “applications”), andmetadata indicative of various characteristics of the file. Metadatasuch as the creating user identifier, one or more editing useridentifiers, creation date/time, edit date(s)/time(s), file size, filename, encryption, and/or the like may be reflected within the metadataaccompanying the file.

Files may be generated at client devices 101A-101N, 102. As mentioned,files may be disseminated as attachments to messages, emails, events,and/or the like. Accordingly, files may be disseminated in accordancewith the various processes discussed herein in instances in which thosefiles are attached to another work object.

Examples of files that may be disseminated as work objects comprise:audio, video, presentations, vectors, spreadsheets, disk images, zipfiles, executable files, media archives, CAD files, 3D graphics,database instances, binary files, markdowns, HTML, code, CSS, PHP, Word®documents, Excel® spreadsheets, PowerPoint® presentations, Illustrator®files, Photoshop® files, LightRoom® files, InDesign® files, Flash,iPhone apps, Android apps, Dropbox® files, Box® files, Origami® files,Sketch® files, and/or the like. However, it should be understood thatthis listing of files is merely a listing of examples, and other filetypes may be disseminated in accordance with various embodiments hereof.

File Intake and Dissemination

As discussed above, files may be disseminated independently, or filesmay be disseminated as attachments to other work objects disseminated inaccordance with one or more methodologies, such as those discussedherein. Once the file and its related work object are received at thegroup-based communication platform 105, the file may be detached fromthe holding work object and indexed separately for later retrieval.

FIG. 13 illustrates an example process for intake processing of filesinto the group-based communication platform 105. The process illustratedin FIG. 13 demonstrates how an example file may be transmitted with amessage (one type of work object discussed herein) transmitted from aclient device 101A-101N, however it should be understood that files maybe disseminated with emails (or other work objects) originating from aclient device 102 disseminated work objects through one or morevalidated external resources 112A-112N. Thus, the process shown in FIG.13 merely shows steps for intaking files for indexing, and does notprovide additional detail of dissemination processes, which areperformed in a manner consistent with those discussed above formessages, emails, and/or events (the messages may be disseminated asattachments to other work objects).

As shown at Block 1301, a file may be generated and/or otherwiseappended to a message for dissemination among a plurality of clientdevices 101A-101N, 102. As mentioned above, this illustration is justone example, as files may be disseminated as an attachment to an email,an event, or another work object, or files may be disseminatedindependently under certain circumstances.

As shown at Block 1302, the message (or other work object) with theattached file is received at the group based communication platform 105(specifically, at the operation servers 107A-107N). The operationservers 107A-107N (or another component of the group based communicationplatform 105) separate the file from the message (or other work object),as indicated at Block 1303, such that the files may be parsed andindexed separately for later retrieval.

The operation servers 107A-107N identify what type of work object isreflected by the file. The identity of the work object type may beutilized to determine an appropriate methodology for parsing the workobject and/or for identifying data to be retrieved from the work objectduring parsing. Thereafter, the group-based communication platform 105parses context data of the file, as shown at Block 1304, and provide thefile to the database storage areas 108A-108N. While parsing the file,the operation servers 107A-107N identify content of the file (ifpossible), and may identify one or more other characteristics of thefile that may be extracted from the file. For example, the operationservers 107A-107N may identify one or more appropriate applications toexecute the particular file and/or to provide preview functionality forthe file, and may, in certain circumstances, utilize the application (ifdirectly available to the group-based communication platform) togenerate a visual preview of the file contents.

In certain embodiments, parsing the file may comprise extracting andreviewing context data, such as metadata provided together with thefile. The metadata provided with the file may be indicative of what typeof file is represented therein. In certain embodiments, certain filetypes may be characterized by the metadata provided in accordance withthe particular file type. Document files may be characterized bymetadata indicative of the file type (e.g., identified by a fileextension), file title, content, creation date, and author. Spreadsheetfiles may be characterized by metadata indicative of the file type(e.g., identified by a file extension), file title, content, creationdate, and author. Presentation files may be characterized by metadataindicative of the file type (e.g., identified by a file extension), filetitle, content, preview data, creation date, and author. Image files maybe characterized by metadata indicative of the file type (e.g.,identified by a file extension, such as .jpg, .png, .gif, and/or thelike), file title, image, size (Ko, Mo), and preview data. Video filesmay be characterized by metadata indicative of the file type (e.g.,identified by a file extension, such as .mpg, .mp4, and/or the like),file title, video, thumbnail data, length, and size (Ko, Mo). Audiofiles may be characterized by metadata indicative of the file type(e.g., identified by a file extension (e.g., .mp3, .wav, and/or thelike), file title, audio, length, and size (Ko, Mo). Task files may becharacterized by metadata indicative of the file type (e.g., identifiedby a file extension), file title, description, assignee, and due date.Other files may be characterized by metadata indicative of the file type(e.g., identified by a file extension), file name, size, and preview.

In certain embodiments, the group-based communication platform 105retrieves the substantive content of the file (if applicable), which maybe utilized for searching and/or classification of the file. Moreover,the group-based communication platform 105 parses various portions ofthe metadata included with the file to identify relevant characteristicsof the file usable for indexing the event, for classifying the file,and/or otherwise for providing the file to various intended recipients.For example, characteristics unique to files, such as programs usablefor executing those files, may inform whether a file should be presentedto a searching user (e.g., a file may not be presented to a clientdevice 101A-101N, 102 that does not include capabilities of utilizingthe file.

In certain embodiments, the group-based communication platform 105identifies a sender/generator of a file by parsing the metadata receivedwith the file (and/or the metadata associated with a work object thatcontained the file, if applicable). The sender may be identified by asending email address, a sending user identifier (particularlyapplicable for internal work objects), a validated external resourceidentifier, and/or the like. The group-based communication platform maythen determine whether the sender matches any profiles or otheruser-identifying data stored at the group-based communication platform105, if not already identified based on the user identifier (e.g.,stored within databases 108A-108N). Determining whether the sendermatches existing user profiles may be utilized to identify a sender'sexpertise, which may be relevant for establishing appropriate topics forthe file.

The group-based communication platform 105 may further determine whetherthere are any security and/or sharing concerns applicable to the filewhile parsing the same. The group-based communication platform 105determines what client devices 101A-101N, users, groups, and/or the likemay access the file, which may dictate how the file is utilized and/orindexed (e.g., the security and/or sharing determination may establishwhich work object corpus the file is to be added to).

Moreover, the group-based communication platform may determine whetherany other characteristics exist that are unique to the file. Forexample, particular event-based validated external resources may providespecific metadata content in files that may be utilized by thegroup-based communication platform 105 in establishing supplementalmetadata for the file (as discussed herein). For example, specificformatting data may be utilized for identifying appropriate formattingcorollaries for use with the cache objects.

Moreover, while parsing the file, the operation servers 107A-107N maygenerate a lightweight summary cache object representative of the filefor rendering within visual containers by client devices 101A-101N thatultimately receive the file as a work object via the group-basedcommunication platform 105. The summary cache object may comprise atleast a portion of the file (e.g., the file name and/or the fileextension), and may include an icon representative of the fileextension. As determined based at least in part on the results of theparsing process, a plurality of icons may be identified as applicable toa particular file (e.g., each correlating to a particular applicationcapable of utilizing the file). These multiple icons may be provided tothe client device 101A-101N when providing the summary cache object tothe client device 101A-101N, which may then select an appropriate iconbased on a default program installed and utilized by the client device101A-101N to utilize the file type. In other embodiments, the icon neednot be selected at all at the group-based communication platform 105,and instead the summary cache object may be provided to the clientdevice 101A-101N with an executable portion configured to query theclient device 101A-101N to determine an icon applicable to theparticular file type.

Moreover, the operation servers 107A-107N may generate an expanded cacheobject having additional detail of the file to be associated with thefile and the summary cache object. In certain embodiments, the operationservers 107A-107N may be configured to generate the expanded cacheobject for only a subset of all files, for which the operation servers107A-107N are configured to (or are configured to operate in associationwith an application that is configured to) execute and view the contentsof the file itself. As just one example, the expanded cache object for afile may comprise a visual preview of the contents of the file (e.g., animage of a first page of a .pdf file; an image of a three-dimensionalobject reflected within a Computer-Aided Drafting (CAD) file, an imageshowing a select number of lines of code within a coding file, an imageshowing a webpage reflected within a .html file, and/or the like). Thevisual preview may be generated at the group-based communicationplatform 105 and/or together with a validated external resource112A-112N capable of utilizing the file. The visual preview may, incertain embodiments, be generated by an emulation software programstored within the database 108A-108N (if available). In otherembodiments, the visual preview may be generated locally at the clientdevice 101A-101N by providing the entire work object to the clientdevice 101A-101N, and enabling one or more programs executable on theclient device 101A-101N to generate a preview of the work object to bedisplayed within the container of the group-based communicationinterface.

The summary cache object for the file may be configured to beinteractive for the receiving client devices 101A-101N, such thatclicking/selecting the summary cache object may cause the client device101A-101N to request an expanded cache object from the group-basedcommunication platform 105, if available. Likewise, the expanded cacheobject may be similarly interactive, and clicking/selecting the expandedcache object may cause the client device 101A-101N to launch anappropriate program/application (e.g., a client-device specified defaultprogram) to execute the file. In instances in which an expanded cacheobject is not available for a file, clicking/selecting the summary cacheobject may cause the client device 101A-101N to launch an appropriateprogram/application to execute the file.

With reference again to FIG. 13, the database storage areas 108A-108Nmay generate and append supplemental metadata to the file after reviewof the same, as indicated at Block 1305. Such supplemental metadata maycomprise metadata indicative of a topic assigned to the file. Moreover,such supplemental metadata may be generated in accordance with one ormore artificial intelligence and/or machine-learning algorithmsconfigured to review the substantive contents of the file (ifaccessible) and/or other metadata associated with the file to determinean appropriate topic to be assigned to the file. In certain embodiments,the topics available for assignment may be established manually by userinput, and the database storage areas 108A-108N may be configured toselect a most-appropriate topic (or multiple topics) from theestablished listing. In other embodiments, the artificial intelligenceand/or machine learning algorithms may be configured for automaticallygenerating a topic in instances in which previously generated topics aredeemed too tenuous for description of the file.

As a specific example, the database storage areas 108A-108N may utilizecontext data of the file, such as the file content (if accessible), filemetadata (e.g., reviewing topics assigned to messages, files, events,message threads, and/or the like in which the file is exchanged;identifying a sending user and determining the sending user's assignedsubject matter expertise to weigh the potential topics that may beassigned to the file), and/or the like to determine an appropriate topicfor the file.

Ultimately, the database storage areas 108A-108N index the file, asshown at Block 1306, which may make the file available for latersearch/retrieval (e.g., for queries satisfying file access requirements,such as meeting authorization prerequisites to view the message). Incertain embodiments, only the metadata and supplemental metadata of thefile may be searchable, if the contents of the file itself are notdirectly searchable (e.g., if the group-based communication platform 105is incapable of rendering the contents of the file).

As stated above, the file may be disseminated as an attachment to amessage, email, event, or as an independent file, in accordance withthose configurations relating to message, email, and eventdissemination, discussed above. The summary cache objects and/orexpanded cache objects corresponding to the file may be rendered withinvisual containers displayed on receiving client devices 101A-101N.

Tasks

In some embodiments of an exemplary group-based communication platform105, a task, task list, or other internal work object may be transmittedfrom a client device 101A-101N to a group-based communication platform105. In yet other embodiments, a task or task list may be embodied as anexternal work object usable with a validated external resource 112A-112Nconfigured for managing a user's task list. In the latter embodiments,the validated external resource 112A-112N may provide tasks, taskslists, and/or the like as external work objects for indexing within adatabase storage areas 108A-108N of the group-based communicationplatform 105. In either embodiment, tasks or task lists are sent to thegroup-based communication platform 105 over communication network 103directly by one or more of the client devices 101A-101N, or by one ormore validated external resources 112A-112N. Like other work objectsdiscussed above, tasks or task lists may be transmitted to thegroup-based communication platform 105 via an intermediary. In oneimplementation, a task may include data such as a task identifier, auser identifier associated with the task (e.g., a user generating thetask), a delegate identifier (e.g., another user identifier associatedwith a user to whom the task is delegated), a task description, a tasklocation, a task start date (and/or time), a task due date (and/ortime), one or more task reminder dates and/or times, a completion statusof the task, and/or the like. Task lists may comprise one or more tasks(each task comprising data as noted above), and may comprise additionaldata such as a user identifier associated with the task list, a tasklist identifier, and/or the like.

In certain embodiments, tasks and/or task lists may be embodied aspersonal work objects to a particular user. These work objects are notshared with users beyond the user associated with the task or task list.However, as discussed in greater detail herein, such work objects may beindexed by the group-based communication platform 105 such thatcharacterizations of other, public or non-personal work objects and/ordetermined relationships and similarities with the personal work objectsmay be utilized to characterize the personal work objects. As discussedherein, such characterizations may facilitate search queries andretrieval of these personal work objects by the associated user. Forexample, personal work objects embodied as tasks or task lists may beadded to work graph data structures for establishing links with other(potentially non-personal work objects). Although the personal workobjects remain inaccessible to other users, these established links mayprovide additional characterization data for the personal tasks or tasklists, which may facilitate later search and retrieval of the task ortask list by users having access to the task or task list (specifically,access to the content of the task or task list). Moreover, as notedabove, personal work objects such as tasks or task lists may berepresented within work graph data structures as encrypted data, therebyfurther preventing unauthorized access to the underlying content of thepersonal work object by unauthorized users.

In certain embodiments, attachments may be included with a task. Theseattachments may, as discussed above, constitute separate work objects(e.g., files, events, messages, emails, and/or the like), which may bereceived and processed by operation servers 107A-107N in accordance withtheir respective work object type.

As discussed herein, work object context data, such as metadata and/orother contents of the task or task list may be used to index the task ortask list, to facilitate various facets of searching (i.e., searchqueries that return results from the operation servers 107A-107N),and/or to otherwise establish relationships with other work objects(e.g., messages, other tasks, emails, events, and/or the like). Metadataassociated with the task or task list may be determined and the task maybe indexed in the database storage areas 108A-108N. In one embodiment,the task or task list may be indexed such that the task or task listassociated with particular users are stored separately. In oneimplementation, tasks or task lists may be indexed at a plurality ofseparate distributed repositories (e.g., to facilitate scalability). Ifthere are attachments associated with task or task list, file contentsof the associated files may be used to index such files and tasks in theoperation servers 107A-107N to facilitate searching. Moreover, asdiscussed herein, because certain tasks and task lists are inherentlypersonal to a user, those tasks and task lists may be indexed andrendered searchable only to the user(s) to which the tasks or task listsare assigned. In certain embodiments, the contents of tasks or tasklists may be usable to establish a particular user's expertise in asubject (and accordingly such tasks and task lists may be representedwithin a work graph), although the underlying tasks and task lists maynot themselves be searchable and/or accessible to other users.

Task Intake and Distribution

In the illustrated embodiment of FIG. 14, which shows an example flow ofdata relating to the generation and indexing of tasks, tasks aregenerated by and received from client devices 101A-101N interactivedirectly with the group-based communication platform 105. However, itshould be understood that in certain embodiments, tasks and task listsmay be maintained by one or more validated external resources 112A-112N(e.g., dedicated task management validated external resources), andaccordingly tasks may be provided from client devices 102, to validatedexternal resources 112A-112N before being provided to the group-basedcommunication platform 105 in accordance with certain embodiments.

As mentioned, tasks and task lists are initially generated at clientdevices 101A-101N, as shown at Block 1401. Tasks and task lists aregenerated in response to user input received at the generating clientdevice 101A-101N, and are indicative of the content that the userintended to be reflected in a task by way of the generated task or tasklist. For example, a user may maintain a task list for all tasksrelating to starting a new business (and in such a case, the task listmay be characterized by a task list identifier of “New Business Tasks”).The user's New Business Tasks, task list may include a number ofindividual tasks, each having their own task identifier, completionstatus, description, and other data as discussed above. For example, onetask may have a task identifier of “apply for new business license,”with a start date of January 1, a due date of June 1, a description of“file paperwork with secretary of state,” and a completion status of“Not Started.” The task may also include data indicative of a delegateof the user's assistant (identified based on the assistant's useridentifier). Moreover, the task may also include an attachment, such asa document including the blank paperwork that must be completed andsubmitted to the secretary of state.

As should be understood, various portions of the task may containalphanumeric text, emojis, and/or other input provided by the user. Thecontent generated by the user (e.g., via user input) is combined withother context data generated by and/or relating to the client device101A-101N and applicable to the task. This context data includesmetadata to enable the task to be appropriate parsed, disseminated,and/or displayed via the client device 101A-101N and/or group-basedcommunication platform 105.

The generated task or task list is passed to the group-basedcommunication platform 105, specifically to one or more of the operationservers 107A-107N. The operation servers 107A-107N receive the generatedtask or task list (as shown at Block 1402) and prepare the task or tasklist for storage and/or distribution for access by the appropriateusers.

The operation servers 107A-107N identify what type of work object isreflected by the task or task list. The identity of the work object typemay be utilized to determine an appropriate methodology for parsing thework object and/or for identifying data to be retrieved from the workobject during parsing. Thereafter, the operation servers 107A-107Ndetermine various characteristics of the task or task list by parsingthe task or task list metadata, as indicated at Block 1403. Whileparsing the task or task list, the operation servers 107A-107Nidentifies content of the task or task list, and may identify one ormore other characteristics of the task or task list that may beintegrated with various configurations of the group-based communicationplatform 105. Moreover, in the event that the task or task list wasgenerated by a client device 102 interacting with a validated externalresource 112A-112N, the operation servers 107A-107N identifies agenerator of the task/task list based on a validated externalidentifier. The group-based communication platform may then determinewhether the generator matches any profiles or other user-identifyingdata stored at the group-based communication platform 105 (e.g., storedwithin databases 108A-108N). Determining whether the generator matchesexisting user profiles may be utilized to identify the generator'sexpertise, which may be relevant for establishing appropriate topics forthe task or task list. Similar processes may be utilized to determinewhether an identifier corresponding to a delegate of a task or task listmatches any profiles or user-identifying data stored at the group-basedcommunication platform 105. Similarly, such data may be utilized toestablish an expertise of the delegate.

Moreover, the group-based communication platform may determine whetherany other characteristics exist that are unique to the task or tasklist. For example, particular task-based validated external resources112A-112N may provide specific metadata contents in tasks that may beutilized by the group-based communication platform 105 in establishingsupplemental metadata for the task or task list (as discussed herein).

Moreover, while parsing the task or task list, the operation servers107A-107N may generate a lightweight summary cache object representativeof the task or task list for rendering within visual containers byclient devices 101A-101N that ultimately receive the task or task listas a work-object via the group-based communication platform 105. Thesummary cache object may be constructed from portions of the contextdata of the task or task list, which may be inserted into a summarycache object template. Other portions of the template may be selectedand/or populated with data generated by the group-based communicationplatform 105. The summary cache object may comprise at least a portionof the content of the task or task list (e.g., the title/identifier, thedue date, and/or the like). In certain embodiments, the summary cacheobject may omit formatting data, and may instead rely on localformatting mechanisms stored locally on the client devices 101A-101N forrendering the summary cache object.

Moreover, the operation servers 107A-107N may generate an expanded cacheobject having additional detail of the task or task list (e.g., theentirety of the task or task list content), certain formattingcharacteristics, attachments, and/or the like) to be associated with thetask or task list and the summary cache object. The summary cache objectmay then be configured to be interactive for the receiving clientdevices 101A-101N, such that clicking/selecting the summary cache objectmay cause the client device 101A-101N to request the expanded cacheobject from the group-based communication platform 105. Likewise, theexpanded cache object may be similarly interactive, andclicking/selecting the expanded cache object may cause the client device101A-101N to request the full task or task list from the group-basedcommunication platform 105.

Moreover, in certain embodiments, the operation servers 107A-107N passthe task or task list to one or more database storage areas 108A-108Nfor indexing. The databases may generate and append supplementalmetadata to the task or task list after review of the context data, asindicated at Block 1404. Such supplemental metadata may comprisemetadata indicative of a topic assigned to the task or task list.Moreover, such supplemental metadata may be generated in accordance withone or more artificial intelligence and/or machine-learning algorithmsconfigured to review the context data, such as the substantive contentsof the task or task list and/or the metadata associated with the task todetermine an appropriate topic to be assigned to the task or task list.Particularly for task lists, metadata associated with individual tasksstored within the task list may be utilized to determine an appropriatetopic for assignment to the task list. In certain embodiments, thetopics available for assignment may be established manually by userinput, and the database storage areas 108A-108N may be configured toselect a most-appropriate topic (or multiple topics) from theestablished listing. In other embodiments, the artificial intelligenceand/or machine learning algorithms may be configured for automaticallygenerating a topic in instances in which previously generated topics aredeemed too tenuous for description of the task or task list.

As a specific example, the database storage areas may utilize contextdata of a task, such as the task description, task identifier, and/orthe like (which may be reviewed utilizing a Tf-idf algorithm in light ofa larger database of tasks to identify relevant topics), task metadata,and/or the like to determine an appropriate topic.

Ultimately, the database storage areas 108A-108N index the message, asshown at Block 1405, which may make the message available for latersearch/retrieval. As mentioned above, tasks and task lists may be madeavailable to a limited number of users (e.g., the generating user and/ora delegate of the task), and accordingly these tasks and task lists maybe searchable by only the generating user and the delegate of the task.

For tasks embodied as internal work objects of the group-basedcommunication platform 105, the operation servers 107A-107N may appendthe task to an assigned task list, if applicable, and as indicated atBlock 1406. It should be understood that similar procedures may beexecuted by validated external resources 112A-112N with respect to tasksimplemented as external work objects. Such processes may compriseinserting data indicative of the task within task list data existing fora particular user.

If applicable, the task or task list may be disseminated to one or moreclient devices 101A-101N, as indicated at Block 1409. Tasks or tasklists delegated to particular users may be disseminated to clientdevices 101A-101N associated with the delegated users. In otherembodiments, tasks and task lists kept private to a particular user maybe delegated to one or more client devices 101A-101N associated with theparticular user. Moreover, although not shown, various embodiments mayfurther disseminate one or more tasks or task lists to validatedexternal resources 112A-112N to update tasks or task lists storedthereon.

Due to the time-specific nature of certain events, the group-basedcommunication platform 105 may establish various time-based delivery,reminder, alert, and/or other configurations for providing informationto users identified as associated with (or delegated to) a particulartask. For example, the group-based communication platform 105 may beconfigured to generate delayed delivery messages for dissemination toone or more of the intended recipients at established times (e.g., at aspecified time prior to the due date of a task). Characteristics ofthese delayed delivery messages (or other alerts, reminders, and/or thelike) may be generated in accordance with various characteristics of thetask, such as a defined due time, due date, and/or the like for thetask.

Recipient client devices 101A-101N receive the task or task list (whichmay include a newly added task) as indicated at Block 1408 and mayrender those tasks or task lists (e.g., using style guides storedlocally on those client devices 101A-101N) as indicated at Block 1409.

Example Implementation

Work objects in accordance with various embodiments may be disseminatedbetween and among a plurality of client devices 101A-101N, 102 inaccordance with the various embodiments discussed above. Theseembodiments thereby enable one or more work objects to be shared amongone or more client devices 101A-101N, 102, thereby allowing users toshare content, ideas, and/or the like in any format deemed mostconvenient to the users. Moreover, users are not limited tocommunicating within the restrictive confines of a particularcommunication platform, which may be limited to particular communicationcharacteristics, such as non-real-time communications, size-restrictedcommunications, attachment-restricted communications, and/or the like.

Caching and Reformatting

Various configurations facilitate the exchange of various work objectsbetween client devices 101A-101N, 102 through processes for generatingrelatively lightweight (small file size) cache objects that may bepassed directly to and stored within the memory of receiving clientdevices 101A-101N, 102 without immediately and in real-time passinglarger, original work objects to client devices 101A-101N, 102 unlessexplicitly requested. For example, the group-based communicationplatform 105 may be configured to generate a summary cache object foreach of one or more work objects, which includes a minimal amount ofinformation regarding the related work object (e.g., a title and a smallsnippet of the contents of the work object). The summary cache object,which is described in various forms throughout this description, may betransmitted in real-time to intended recipients of a particular workobject, thereby enabling those intended recipients to identify when awork object is received and generally what the work object is. Thesesummary cache objects may be indexed together with the underlying workobject itself, such that when a particular work object is uncovered as aresult of a search query (discussed herein), the search results may beprovided to a requesting client device 101A-101N, 102 in the form of alisting of summary cache objects, rather than providing large workobjects directly to a client device in response to a query.

Moreover, the group-based communication platform 105 may generateexpanded cache objects and indexed together with the underlying workobjects. These expanded cache objects may be considered to beintermediate in size, having more detail than the respective summarywork objects, but still lacking some of the detail of the complete workobject. In certain embodiments, the expanded cache objects (variousforms of which are discussed herein) encompass additional detailregarding the contents of a particular work object. These expanded cacheobjects may be provided to client devices 101A-101N, 102 in response tospecific requests. For example, requesting additional detail for aparticular summary cache object may cause the client device 101A-101N,102 to generate and transmit a request for a related expanded cacheobject to the group-based communication platform 105, which may includedata sufficient to identify the underlying work object and an indiciathat the expanded cache object is requested. The group-basedcommunication platform 105 may then identify a relevant expanded cacheobject and may transmit the relevant expanded cache object to the clientdevice 101A-101N, 102, which may replace the displayed summary cacheobject with the expanded cache object (e.g., graphically, the clientdevice 101A-101N, 102 may cause the displayed summary cache object tographically expand to encompass the additional data included within theexpanded cache object).

It should be understood that the expanded cache object may not includeduplicate data of that included within the summary cache object, beyonda minimal amount of identifying data needed to match the summary cacheobject, the expanded cache object, and the underlying work objecttogether. In such embodiments, providing the expanded cache object tothe client devices 101A-101N, 102 may encompass providing additional,expansive data to the client devices 101A-101N, 102 regarding theparticular work object, and the client device may then match the newlyreceived expansive data with the already stored summary cache data tolocally generate the complete expanded cache object for display to auser.

Ultimately, as discussed herein, a client device 101A-101N, 102 mayfurther request the full work object to be provided to the client device(e.g., in response to a user interaction) in a manner similar torequesting the expanded cache object, for example, by identifying theunderlying work object and providing an indicia that the full workobject is requested. The group-based communication platform 105 may thenretrieve the requested work object and may transmit the same to therequesting client device 101A-101N, 102. The client device 101A-101N maythen use a relevant locally executable application forexecuting/utilizing the full work object, and the relevant locallyexecutable application may be selected based at least in part on thework object type.

In certain embodiments, the group-based communication platform 105 isfurther configured to reformat various work objects and/or cache objectsto visually fit naturally within the group-based communicationinterface. For example, while parsing the work object and/or whilegenerating cache objects to be associated with the work object, thegroup-based communication platform 105 may be configured to identifyformatting attributes of content of the underlying work object.

For example, the group-based communication platform 105 may identify aformatting style sheet, may identify particular formatting attributes ofmetadata associated with the work object, and/or the like. Thegroup-based communication platform 105 may then identify formattingcorollaries within a group-based communication platform-specific stylesheet, such that those correlated styles may be applied to the workobject (or cache object) for display to a user. In certain embodiments,identifying style corollaries may be performed via a matching algorithm,having known formatting attributes of various work objects mapped toformatting corollaries of the group-based communication platform (e.g.,a formatting indication of bold within a .css file may be mapped withinan applicable formatting data table stored within the database storageareas 108A-108N to a corresponding bold formatting provided within thegroup-based communication platform-specific formatting guide).Alternatively, style corollaries may be identified via one or artificialintelligence and/or machine learning algorithms trained via an existingformatting corollaries data table, such that formatting may beconfigured to accommodate new work object types generated in the future.

Formatting corollaries may be identified based at least in part on thework object type. Different matching, machine learning, and/orartificial intelligence may be utilized for different work object types.For example, internal work objects may bypass formatting algorithmsentirely, because such internal work objects may be generated to have asuitable formatting structure for use with the group-based communicationplatform 105. In other embodiments, the internal work objects mayutilize specifically configured algorithms for preparing those workobjects for distribution to one or more validated external resources.Accordingly, the one or more algorithms utilized for generatingformatting corollaries for internal work objects may be selected basedat least in part on the one or more validated external resources toreceive the work object.

Moreover, one or more algorithms for formatting one or more externalwork objects may utilize locally stored (at the group-basedcommunication platform 105) copies of style sheets applicable to variousexternal work objects that may be received at the group-basedcommunication platform 105 from one or more validated external resources112A-112N. These style sheets may be utilized to establish formattingcorollaries between work objects usable by the group-based communicationplatform 105 and work objects provided by various validated externalresources 112A-112N. In certain embodiments, various algorithms, such asmachine learning algorithms, artificial intelligence algorithms,matching algorithms, and/or the like may be built automatically at thegroup-based communication platform 105 based at least in part on thesestyle sheets.

Moreover, it should be understood that different portions (e.g.,different fields) of work objects may be subject to different formattingrequirements, different formatting corollaries, and/or the like. Thus,formatting of work objects to be provided to various client devices101A-101N and/or for providing to various validated external resources112A-112N may utilize a plurality of formatting algorithms, formattingcorollaries, and/or the like.

Generating Supplementary Metadata

The group-based communication platform 105 of certain embodiments isconfigured to generate and append supplementary metadata to work objectsto facilitate the generation of a work graph demonstrating relationshipsbetween various work objects and to facilitate later search queries(e.g., topic-based search queries). As just one example, topics forcertain work objects may be assigned based on user input, such as usersself-assigning particular topics to certain work objects. Topics may beassigned manually by users placing a hashtag phrase within the workobject (e.g., “#patents”). The group-based communication platform 105may be configured to provide a high level of deference tomanually-assigned topics, such that these topics are deemed the primarytopic of the associated work object.

In other embodiments, the contents and/or metadata of a particular workobject may be reviewed by the group-based communication platform (e.g.,via one or more artificial intelligence and/or machine learningalgorithms) to identify an underlying topic of the work object. Anappropriate model for generating an underlying topic for a work objectmay be selected based at least in part on the work object type. Topicsource data (e.g., indicative of available topics) and data utilized bythe model for learning topic assignment concepts, may be shared acrosswork-object-specific models, as the source data may be retrieved from acomplete work object corpus. The topics may be determined based on asingle work-object alone, or may be determined based on contextsurrounding a particular work object, such as based on other workobjects exchanged within a common thread (e.g., a plurality of messagescollectively defining a conversation surrounding the work object inquestion) and/or other work objects existing within a common task list(e.g., a plurality of tasks collectively defining a task listencompassing the work object in question). In certain embodiments, amodel utilized to establish a work object topic may determineapplicability of certain aspects of a work object to historical data.The group-based communication platform 105 may be configured to identifysimilar types of context data (even if not identical) utilized toestablish similarities between work objects. For example, a userassociated with a particular work object (e.g., a participant in anevent; a recipient of an email; a recipient of a message) may beutilized to establish similarities between work objects. The group-basedcommunication platform 105 reviews context data of various work objectsand applies one or more algorithms to give appropriate weight to variousportions of the work object in assigning an applicable topic.

In certain embodiments, a plurality of topics may be assigned to aparticular work object, and these topics may be ranked by relevance tothe work object. The most relevant topics (e.g., those manually assignedtopics and/or the most relevant automatically assigned topics) may begiven greater weight in establishing whether a particular work object isrelated to a particular topic than topics deemed the least relevant to aparticular work object.

In various embodiments, the group-based communication platform 105 maybe configured to automatically generate a summary for a particular workobject, to be indexed together with the underlying work object itself.This summary may then be presented within a search results listing inwhich the work object is a part of, such that a user may gain a generalunderstanding of the contents of the work object without requesting thework object or a corresponding cache object associated with the workobject. The summary may be presented in a natural language formatdescribing the type of work object and the content of the work object.These summaries may be generated automatically, for example, based atleast in part on one or more artificial intelligence and/or machinelearning algorithms configured to self-learn sentence structure andrelated topical relationships to self-generate summaries of various workobjects. As just one example, a summary of a particular email may begenerated to read “An email from Amy to Sue discussing document displayafter unfurling.”

Generating a Work Graph of Work Objects

Work objects may be stored in one or more database storage areas108A-108N during applicable indexing procedures as discussed herein.Moreover, such work objects may be stored as entries of a graphicaldatabase (or a relational database providing similar functionality forillustrating relationships between work objects, or any of a variety ofother database storage structures for providing similar data storageconfigurations), providing data illustrative of generated relationshipsbetween various work objects. Those relationships between work objectsmay be generated based at least in part on the supplemental metadatagenerated and appended to various work objects, and collectively therelationships between work objects define a work graph illustratingrelationships among a plurality of work objects, which may be usable byone or more artificial intelligence-based search systems for identifyinga plurality of inter-related work objects to be presented in response toa particular search query. In certain embodiments, work objects storedwithin a work graph are each characterized by their own accesscredentials/requirements. Accordingly, some work objects within the workgraph may only be accessible to a select group of users (e.g., a singleuser), whereas other work objects within the same work graph may beaccessible to a larger/different group of users (e.g., all usersassociated with a particular group). Despite these differences inaccessibility between various work objects within a common work graph,relationships established between various work objects may be usable toestablish topics for various work objects, for establishing a particularuser's expertise, to determine relatedness of work objects for searchqueries, and/or the like.

For each work object, the database storage areas 108A-108N, theoperation servers 107A-107N, or other components of the group-basedcommunication platform 105 may perform an analysis of the contentsand/or metadata (e.g., metadata provided with the work object) and/orsupplemental metadata generated by the group-based communicationplatform 105 to determine other work objects deemed sufficientlyrelevant to illustrate a connection within the work graph).

An example process is shown in the flowchart of FIG. 15. As showntherein, the process may begin by selecting a work object for analysis,as shown at 1501. The work object's relationship to other work objectsmay then be determined at 1502. In certain embodiments, the group-basedcommunication platform 105 may identify shared topics within metadata ofthe work object and other work objects; identify common sending useridentifiers; identify common participants (a greater number orpercentage of shared participants may provide a stronger indicatedrelationship); identify common work object types; identify commonintended recipients; identify temporal relationships betweengeneration/transmission of work objects; and/or the like.

As shown at Block 1503, the group-based communication platform mayestablish weighted relationship scores between each of the other workobjects identified at step 1502. For example, stronger relationships(e.g., a higher number of shared characteristics), or certain types ofrelationships (e.g., as identified via a machine learning algorithm) mayresult in a higher relationship score between the analyzed work objectand one or more other work objects. These relationship scores may beranked (e.g., by direct comparison of relationship scores, bynormalization of comparison scores on a shared scale (e.g., 0-1), and/orthe like). In certain embodiments, those relationship scores satisfyinga first degree score criteria (e.g., exceeding a score threshold) may beutilized to establish direct relationships between the analyzed workobject and those other work objects having a sufficient relationshipscore, as suggested at Block 1504. Those first degree scores may then bemapped within the work graph, as shown at Block 1505 (e.g., byestablishing edges between data indicative of work objects within agraphical database, by providing data indicative of related work objectswithin data of a particular work object database entry within arelational database, and/or the like). The process of FIG. 15 may thenbe repeated for each work object, while accommodating thoserelationships that have already been established from prior iterations.It should be understood that, in accordance with certain embodiments,relationships between various work objects may be symmetrical (e.g., thedegree of relatedness of a first work object to a second work object isidentical to the degree of relatedness of the second work object to thefirst work object). However, it should be understood that in otherembodiments, the relationships between various work objects may beasymmetrical (e.g., the degree of relatedness of a first work object toa second work object is not identical to the degree of relatedness ofthe second work object to the first work object).

A graphical depiction of an example work object is shown at FIG. 16,which illustrates relationships (indicated by lines) between variouswork objects (depicted as blocks).

As is evident from the illustration of FIG. 16, the work graph providesan indication of direct, first degree relationships between various workobjects, as well as indirect relationships established between workobjects through intermediate work objects. These indirect relationshipsmay be indicated as second degree relationships, third degreerelationships, and/or the like, indicative of the number of degrees ofseparation between work objects within the work graph. As discussedherein, these indirect relationships may be reflected within (orotherwise influence, through characteristics of artificial intelligencemodels) search results provided to a user in response to a query forwork objects. In other configurations, indirect relationships may beaccessible to users via a browsing-like functionality, in which a usermay click through a plurality of work objects, wherein data indicativeof other, related work objects may be presented for each viewed workobject, such that the user may click and browse through to any of thoseidentified related work objects.

Moreover, through the work graph's illustration of relationships betweenvarious work objects, the work graph may also be utilized to determinerelationships between users, between users and channels, between usersand topics, between channels and topics, between channels, betweentopics, between users and work objects, between channels and workobjects, between topics and work objects, and/or the like. Thus, thework graph may be configured to establish relationships between workobjects, and those relationships may be further utilized to identifyrelationships between other aspects of data utilized with thegroup-based communication platform 105 (such as data indicative ofparticular users, channels, groups, and/or the like).

In certain embodiments, through identified relationships betweenparticular users and certain work objects, a topic expertise may beestablished for the particular user (and assigned to a user identifierassociated with the user), based at least in part on relationshipsestablished and mapped within the work graph. As a part of thedetermination of a particular user's expertise in a particular topic,the group-based communication platform 105 may be configured todetermine the recency with which a particular user interacted with aparticular object having an established topic, the mechanism throughwhich the user interacted with the particular object (e.g., did the usergenerate/send the work object, was the user an intended recipient of thework object, and/or the like), the number of work objects having adefined topic with which the user is related, and/or the like.

The group-based communication platform 105 (e.g., via the databasestorage areas 108A-108N, via the operation servers 107A-107N, and/or thelike) utilizes the work graph to generate a machine learning structure(e.g., a neural network) that may be utilized for executing searchqueries for users. For example, the group-based communication platformmay implement an unsupervised learning structure, a supervised learningstructure, a reinforcement learning structure, a deep learningstructure, and/or the like for utilizing relationships established viathe work graph to generate search results for various work objects.

In certain embodiments, a global machine learning algorithm may beutilized for all work objects stored at or accessible via thegroup-based communication platform 105. In such embodiments, access toparticular work objects (e.g., via a search query utilizing themachine-learning algorithm) may be limited based at least in part onaccess privileges of the searching user (e.g., a user may only be ableto access work objects associated with a particular group, of which theuser is a member). In other embodiments, machine learning algorithms maybe established independently for each of a plurality of groups, suchthat training of the machine learning algorithm is based on work objectsexchanged within the particular group alone.

The machine learning algorithms may be generated and/or updatedperiodically, to reflect changes within the work graph that result fromthe addition and/or aging of work objects within the work graph.Moreover, the machine learning parameters (including those parametersindicative of the underlying neural network of the machine learningalgorithm) may be stored within one or more database storage areas108A-108N.

Executing a Query via the Machine Learning Algorithm and Work Graph

A user of the group-based communication platform 105 (e.g.,accessing/exchanging work objects via a client device 101A-101N, 102)may utilize a query functionality of the group-based communicationplatform 105 to identify and/or retrieve work objects deemed relevant tothe user. In certain embodiments, the query functionality is accessiblevia a client device 101A-101N, and provides users with one or moreoptions for searching for relevant work objects. The query functionalitymay be visually embodied in the group-based communication interface as asingle user-fillable field, or the query functionality may have a moreadvanced search interface with a plurality of fields corresponding toparticular attributes of a work object to be retrieved. In eitherconfiguration (whether through natural language processing and parsingof information provided within the single-field search configuration, orthrough parsing of data provided in one or more fields of an advancedsearch configuration, the query functionality may identify relevantportions of the query to be utilized to identify relevant work objects.For example, a user may only provide a particular keyword of interest(such as “fortran”), which the client device 101A-101N and/or thegroup-based communication platform 105 may determine should be used tosearch for relevant topics, relevant work object titles, and/or thelike. In other embodiments, a user may provide a keyword of interesttogether with other narrowing information, such as informationidentifying a work object type, a time/date of generation of a workobject of interest, one or more involved users, a location (ifapplicable), and/or the like. As a non-limiting example, a search withina single-field search bar may encompass a query such as “February 2019Fortran history meeting in Compiler Room with Bob Smith” (similarqueries may be provided with a multi-field search configuration,entering a date into the date field, a work object type into a “type”field (or selecting a work object type from a listing of available workobject types), a keyword search into a keyword field, a locationidentifier into a location field, and a user name into a user field).The search may then be conducted using the provided search limitationsto retrieve data relevant to the selected meeting, as well as anyadditional work objects deemed relevant to the searched meeting.

In certain embodiments, client devices 101A-101N may access the queryfunctionality via the group-based communication interface displayable onthe client device 101A-101N. In certain embodiments, the queryfunctionality may be embodied as a search bar accessible via thegroup-based communication interface. A user may provide a query as userinput into the search bar, which may cause the client device 101A-101Nto generate a query request to the group-based communication platform105. In certain embodiments, the search bar may be characterized byautocomplete functions (e.g., suggesting complete words that a user maydesire to enter as a search term based on letters already typed by theuser) that continually updates search suggestions as the user types. Inother embodiments, the query functionality may be configured to generateand transmit query requests to the group-based communication platform105 in real-time, as the user types. Thus, the search bar maycontinuously update predicted results for a particular search as theuser types additional letters for the search.

Certain embodiments may additionally enable users of client devices 102to access limited query functionality, for example, by enabling users tosend query requests to the group-based communication platform 105 viaone or more validated external resources 112A-112N. In such embodiments,the group-based communication platform 105 may be configured to providequery results back to the user in the form of a responsive work object(e.g., an email generated by the group-based communication platform 105)including results of a query.

Regardless of the source of the query request, once received at thegroup-based communication platform 105, the group-based communicationplatform 105 may provide the query as input into a machine learningalgorithm. Moreover, the group-based communication platform 105 mayprovide one or more search parameters to accompany the query, such astypes of work objects to search for, whether the search should extend toencompass searches for relevant users, channels, topics, and/or thelike, or other parameters as deemed relevant by the user.

The group-based communication platform 105 may then execute the searchquery via the applicable machine learning model. As a part of the searchquery, the group-based communication platform 105 may establish asimilarity ranking between the search term and the one or more workobjects, to identify work objects deemed most relevant to the searchquery. Such ranking may be performed in accordance with the machinelearning algorithm of the search query. Results satisfying applicablecriteria may be provided to the user (e.g., results deemed to have arelevance score higher than an established threshold; the top definednumber of results, such as the most relevant 3 results). It should beunderstood that results may be provided in a mixed format, such thatresults are provided in a list to the user based on relevance score,regardless of work object type. In other embodiments, results may beorganized based on work object type, with the most-relevant work objectswithin each work object type being presented to the user.

In still other embodiments, the group-based communication platform 105may be further configured to utilize work objects identified as relevantto further identify one or more users, channels, and/or topics deemedrelevant to the query as well. As noted above, various characteristicsof a particular work object (e.g., metadata) may be utilized toassociate a particular user, a particular channel, a particular topic,and/or the like with the work object. Thus, the group-basedcommunication platform 105 may utilize such relationships to identifyusers, channels, and topics deemed relevant to the provided searchquery. These additional identified data may be provided to the user(e.g., within a dedicated portion of the search results display).

In certain embodiments, the search query functionality may enable theuser to quickly select a particular work object from within a searchresults listing. In various embodiments, the search results listing maycomprise a listing of cache objects (e.g., summary cache objects)relating to the work objects identified for inclusion within the search.These summary cache objects may be passed to the client device 101A-101Nthat initiated the search for display within the search query resultsdisplay.

Moreover, the search results display may be configured for quicklymoving search results (e.g., selecting a particular summary cacheobject) into one or more communications (e.g., a new message, acommunication channel, and/or the like), such that work objects may bequickly reshared by a user if/when deemed relevant.

Conclusion

Many modifications and other embodiments will come to mind to oneskilled in the art to which this disclosure pertains having the benefitof the teachings presented in the foregoing descriptions and theassociated drawings. Therefore, it is to be understood that thedisclosure is not to be limited to the specific embodiments disclosedand that modifications and other embodiments are intended to be includedwithin the scope of the appended claims. Although specific terms areemployed herein, they are used in a generic and descriptive sense onlyand not for purposes of limitation.

That which is claimed:
 1. A group-based communication platformconfigured for assigning a user expertise to a user identifier, thegroup-based communication platform comprising: one or more memorystorage areas; and one or more processors collectively configured to:receive one or more work objects from a validated external resource,wherein the one or more work objects comprise metadata and body contentdata; assign one or more topics to each of the one or more work objectsbased at least in part on the metadata and body content data; determinea subset of the one or more work objects associated with a useridentifier for a user; determine a level of relationship between theuser and each of the one or more event objects; and establish topicalexpertise associated with the user identifier based at least in part onthe topics of work objects associated with the user identifier and thelevel of relationship between the user and each of the event objects. 2.The group-based communication platform of claim 1, wherein the one ormore work objects comprise event work objects, and wherein determining alevel of relationship between the user and each of the event workobjects comprises determining whether the user participated in each ofthe one or more event work objects.
 3. The group-based communicationplatform of claim 1, wherein the one or more work objects comprise emailwork objects, and wherein determining a level of relationship betweenthe user and each of the email work objects comprises determiningwhether the user was a sending user of the email work objects.
 4. Thegroup-based communication platform of claim 1, wherein the one or morework objects comprise message work objects, and wherein determining alevel of relationship between the user and each of the message workobjects comprises determining whether the user was a sending user of themessage work objects.
 5. The group-based communication platform of claim1, wherein assigning a topic to each of the one or more work objectscomprises utilizing Term frequency-inverse document frequency (Tf-Idf)analysis to identify one or more topics relevant to each work object. 6.The group-based communication platform of claim 5, wherein each of theone or more work objects are event objects, and wherein the Tf-Idfanalysis is performed on a recording associated with the work object. 7.The group-based communication platform of claim 1, wherein the one ormore processors are further configured to generate a work graphidentifying relationships between each of the plurality of work objects,and wherein determining a level of relationship between a useridentifier and each of the one or more work objects comprisesidentifying relationships between work objects associated with the useridentifier.
 8. A computer-implemented method for assigning a userexpertise to a user identifier, the method comprising: receiving one ormore work objects from a validated external resource, wherein the one ormore work objects comprise metadata and body content data; assigning oneor more topics to each of the one or more work objects based at least inpart on the metadata and body content data; determining a subset of theone or more work objects associated with a user identifier for a user;determining a level of relationship between the user and each of the oneor more event objects; and establishing topical expertise associatedwith the user identifier based at least in part on the topics of workobjects associated with the user identifier and the level ofrelationship between the user and each of the event objects.
 9. Thecomputer-implemented method of claim 8, wherein the one or more workobjects comprise event work objects, and wherein determining a level ofrelationship between the user and each of the event work objectscomprises determining whether the user participated in each of the oneor more event work objects.
 10. The computer-implemented method of claim8, wherein the one or more work objects comprise email work objects, andwherein determining a level of relationship between the user and each ofthe email work objects comprises determining whether the user was asending user of the email work objects.
 11. The computer-implementedmethod of claim 8, wherein the one or more work objects comprise messagework objects, and wherein determining a level of relationship betweenthe user and each of the message work objects comprises determiningwhether the user was a sending user of the message work objects.
 12. Thecomputer-implemented method of claim 8, wherein assigning a topic toeach of the one or more work objects comprises utilizing Termfrequency-inverse document frequency (Tf-Idf) analysis to identify oneor more topics relevant to each work object.
 13. Thecomputer-implemented method of claim 12, wherein each of the one or morework objects are event objects, and wherein the Tf-Idf analysis isperformed on a recording associated with the work object.
 14. Thecomputer-implemented method of claim 8, further comprising generating awork graph identifying relationships between each of the plurality ofwork objects, and wherein determining a level of relationship between auser identifier and each of the one or more work objects comprisesidentifying relationships between work objects associated with the useridentifier.
 15. A computer program product comprising at least onenon-transitory computer-readable storage medium having computer-readableprogram code portions stored therein, the computer-readable program codeportions comprising an executable portion configured to cause a computerprocessor to: receive one or more work objects from a validated externalresource, wherein the one or more work objects comprise metadata andbody content data; assign one or more topics to each of the one or morework objects based at least in part on the metadata and body contentdata; determine a subset of the one or more work objects associated witha user identifier for a user; determine a level of relationship betweenthe user and each of the one or more event objects; and establishtopical expertise associated with the user identifier based at least inpart on the topics of work objects associated with the user identifierand the level of relationship between the user and each of the eventobjects.
 16. The computer program product of claim 15, wherein the oneor more work objects comprise event work objects, and whereindetermining a level of relationship between the user and each of theevent work objects comprises determining whether the user participatedin each of the one or more event work objects.
 17. The computer programproduct of claim 15, wherein the one or more work objects comprise emailwork objects, and wherein determining a level of relationship betweenthe user and each of the email work objects comprises determiningwhether the user was a sending user of the email work objects.
 18. Thecomputer program product of claim 15, wherein the one or more workobjects comprise message work objects, and wherein determining a levelof relationship between the user and each of the message work objectscomprises determining whether the user was a sending user of the messagework objects.
 19. The computer program product of claim 15, whereinassigning a topic to each of the one or more work objects comprisesutilizing Term frequency-inverse document frequency (Tf-Idf) analysis toidentify one or more topics relevant to each work object.
 20. Thecomputer program product of claim 19, wherein each of the one or morework objects are event objects, and wherein the Tf-Idf analysis isperformed on a recording associated with the work object.
 21. Thecomputer program product of claim 15, wherein the executable portion isfurther configured to cause the processor to generate a work graphidentifying relationships between each of the plurality of work objects,and wherein determining a level of relationship between a useridentifier and each of the one or more work objects comprisesidentifying relationships between work objects associated with the useridentifier.